Skip to content
Snippets Groups Projects
  • Florent Ramière's avatar
    6ff0fc6d
    Add compression/acks/retry conf to Kafka output plugin · 6ff0fc6d
    Florent Ramière authored
    The following configuration is now possible
    
    	## CompressionCodec represents the various compression codecs
    recognized by Kafka in messages.
    	##  "none" : No compression
    	##  "gzip" : Gzip compression
    	##  "snappy" : Snappy compression
    	# compression_codec = "none"
    
    	##  RequiredAcks is used in Produce Requests to tell the broker how
    many replica acknowledgements it must see before responding
    	##  "none" : the producer never waits for an acknowledgement from the
    broker. This option provides the lowest latency but the weakest
    durability guarantees (some data will be lost when a server fails).
    	##  "leader" : the producer gets an acknowledgement after the leader
    replica has received the data. This option provides better durability
    as the client waits until the server acknowledges the request as
    successful (only messages that were written to the now-dead leader but
    not yet replicated will be lost).
    	##  "leader_and_replicas" : the producer gets an acknowledgement after
    all in-sync replicas have received the data. This option provides the
    best durability, we guarantee that no messages will be lost as long as
    at least one in sync replica remains.
    	# required_acks = "leader_and_replicas"
    
    	##  The total number of times to retry sending a message
    	# max_retry = "3"
    6ff0fc6d
    History
    Add compression/acks/retry conf to Kafka output plugin
    Florent Ramière authored
    The following configuration is now possible
    
    	## CompressionCodec represents the various compression codecs
    recognized by Kafka in messages.
    	##  "none" : No compression
    	##  "gzip" : Gzip compression
    	##  "snappy" : Snappy compression
    	# compression_codec = "none"
    
    	##  RequiredAcks is used in Produce Requests to tell the broker how
    many replica acknowledgements it must see before responding
    	##  "none" : the producer never waits for an acknowledgement from the
    broker. This option provides the lowest latency but the weakest
    durability guarantees (some data will be lost when a server fails).
    	##  "leader" : the producer gets an acknowledgement after the leader
    replica has received the data. This option provides better durability
    as the client waits until the server acknowledges the request as
    successful (only messages that were written to the now-dead leader but
    not yet replicated will be lost).
    	##  "leader_and_replicas" : the producer gets an acknowledgement after
    all in-sync replicas have received the data. This option provides the
    best durability, we guarantee that no messages will be lost as long as
    at least one in sync replica remains.
    	# required_acks = "leader_and_replicas"
    
    	##  The total number of times to retry sending a message
    	# max_retry = "3"