4                         !"# $% )&  '() *+,-./ 012345 67 89:;<=>?@ABCDEFG2 HIJKLdMN`OPQRSTUVWX YZ Y[ Y\]^_`a bc def=`ghijklmn o p qr s tuvwxyz |}CONFIG*Lorg/apache/kafka/common/config/ConfigDef;BOOTSTRAP_SERVERS_CONFIGLjava/lang/String; ConstantValueMETADATA_MAX_AGE_CONFIGMETADATA_MAX_AGE_DOCBATCH_SIZE_CONFIGBATCH_SIZE_DOC ACKS_CONFIGACKS_DOCLINGER_MS_CONFIG LINGER_MS_DOCREQUEST_TIMEOUT_MS_CONFIGREQUEST_TIMEOUT_MS_DOCDELIVERY_TIMEOUT_MS_CONFIGDELIVERY_TIMEOUT_MS_DOCCLIENT_ID_CONFIGSEND_BUFFER_CONFIGRECEIVE_BUFFER_CONFIGMAX_REQUEST_SIZE_CONFIGMAX_REQUEST_SIZE_DOCRECONNECT_BACKOFF_MS_CONFIGRECONNECT_BACKOFF_MAX_MS_CONFIGMAX_BLOCK_MS_CONFIGMAX_BLOCK_MS_DOCBUFFER_MEMORY_CONFIGBUFFER_MEMORY_DOCRETRY_BACKOFF_MS_CONFIGCOMPRESSION_TYPE_CONFIGCOMPRESSION_TYPE_DOCMETRICS_SAMPLE_WINDOW_MS_CONFIGMETRICS_NUM_SAMPLES_CONFIGMETRICS_RECORDING_LEVEL_CONFIGMETRIC_REPORTER_CLASSES_CONFIG%MAX_IN_FLIGHT_REQUESTS_PER_CONNECTION)MAX_IN_FLIGHT_REQUESTS_PER_CONNECTION_DOCRETRIES_CONFIG RETRIES_DOCKEY_SERIALIZER_CLASS_CONFIGKEY_SERIALIZER_CLASS_DOCVALUE_SERIALIZER_CLASS_CONFIGVALUE_SERIALIZER_CLASS_DOCCONNECTIONS_MAX_IDLE_MS_CONFIGPARTITIONER_CLASS_CONFIGPARTITIONER_CLASS_DOCINTERCEPTOR_CLASSES_CONFIGINTERCEPTOR_CLASSES_DOCENABLE_IDEMPOTENCE_CONFIGENABLE_IDEMPOTENCE_DOCTRANSACTION_TIMEOUT_CONFIGTRANSACTION_TIMEOUT_DOCTRANSACTIONAL_ID_CONFIGTRANSACTIONAL_ID_DOCpostProcessParsedConfig (Ljava/util/Map;)Ljava/util/Map;CodeLineNumberTableLocalVariableTablethis2Lorg/apache/kafka/clients/producer/ProducerConfig; parsedValuesLjava/util/Map;LocalVariableTypeTable5Ljava/util/Map; Signaturel(Ljava/util/Map;)Ljava/util/Map;addSerializerToConfig(Ljava/util/Map;Lorg/apache/kafka/common/serialization/Serializer;Lorg/apache/kafka/common/serialization/Serializer;)Ljava/util/Map;configs keySerializer2Lorg/apache/kafka/common/serialization/Serializer;valueSerializer newConfigs5Lorg/apache/kafka/common/serialization/Serializer<*>; StackMapTable~(Ljava/util/Map;Lorg/apache/kafka/common/serialization/Serializer<*>;Lorg/apache/kafka/common/serialization/Serializer<*>;)Ljava/util/Map;(Ljava/util/Properties;Lorg/apache/kafka/common/serialization/Serializer;Lorg/apache/kafka/common/serialization/Serializer;)Ljava/util/Properties; propertiesLjava/util/Properties; newProperties(Ljava/util/Properties;Lorg/apache/kafka/common/serialization/Serializer<*>;Lorg/apache/kafka/common/serialization/Serializer<*>;)Ljava/util/Properties;(Ljava/util/Properties;)Vprops(Ljava/util/Map;)V8(Ljava/util/Map;)V(Ljava/util/Map;Z)VdoLogZLjava/util/Map<**>;(Ljava/util/Map<**>;Z)V configNames()Ljava/util/Set;%()Ljava/util/Set;main([Ljava/lang/String;)Vargs[Ljava/lang/String;()V SourceFileProducerConfig.java,org/apache/kafka/clients/CommonClientConfigs0org/apache/kafka/clients/producer/ProducerConfig java/util/HashMap key.serializer ~ value.serializerjava/util/Properties        (org/apache/kafka/common/config/ConfigDefbootstrap.servers  9org/apache/kafka/common/config/ConfigDef$NonNullValidatorNonNullValidator InnerClasses dA list of host/port pairs to use for establishing the initial connection to the Kafka cluster. The client will make use of all servers irrespective of which servers are specified here for bootstrapping—this list only impacts the initial hosts used to discover the full set of servers. This list should be in the form host1:port1,host2:port2,.... Since these servers are just used for the initial connection to discover the full cluster membership (which may change dynamically), this list need not contain the full set of servers (you may want more than one, though, in case a server is down).  buffer.memory   -The total bytes of memory the producer can use to buffer records waiting to be sent to the server. If records are sent faster than they can be delivered to the server the producer will block for max.block.ms after which it will throw an exception.

This setting should correspond roughly to the total memory the producer will use, but is not a hard bound since not all memory the producer uses is used for buffering. Some additional memory will be used for compression (if compression is enabled) as well as for maintaining in-flight requests.retries java/lang/Integer  rSetting a value greater than zero will cause the client to resend any record whose send fails with a potentially transient error. Note that this retry is no different than if the client resent the record upon receiving the error. Allowing retries without setting max.in.flight.requests.per.connection to 1 will potentially change the ordering of records because if two batches are sent to a single partition, and the first fails and is retried but the second succeeds, then the records in the second batch may appear first. Note additionall that produce requests will be failed before the number of retries has been exhausted if the timeout configured by delivery.timeout.ms expires first before successful acknowledgement. Users should generally prefer to leave this config unset and instead use delivery.timeout.ms to control retry behavior.acks 1java/lang/Stringall-10 The number of acknowledgments the producer requires the leader to have received before considering a request complete. This controls the durability of records that are sent. The following settings are allowed:

  • acks=0 If set to zero then the producer will not wait for any acknowledgment from the server at all. The record will be immediately added to the socket buffer and considered sent. No guarantee can be made that the server has received the record in this case, and the retries configuration will not take effect (as the client won't generally know of any failures). The offset given back for each record will always be set to -1.
  • acks=1 This will mean the leader will write the record to its local log but will respond without awaiting full acknowledgement from all followers. In this case should the leader fail immediately after acknowledging the record but before the followers have replicated it then the record will be lost.
  • acks=all This means the leader will wait for the full set of in-sync replicas to acknowledge the record. This guarantees that the record will not be lost as long as at least one in-sync replica remains alive. This is the strongest available guarantee. This is equivalent to the acks=-1 setting.compression.typenoneqThe compression type for all data generated by the producer. The default is none (i.e. no compression). Valid values are none, gzip, snappy, lz4, or zstd. Compression is of full batches of data, so the efficacy of batching will also impact the compression ratio (more batching means better compression).  batch.size The producer will attempt to batch records together into fewer requests whenever multiple records are being sent to the same partition. This helps performance on both the client and the server. This configuration controls the default batch size in bytes.

    No attempt will be made to batch records larger than this size.

    Requests sent to brokers will contain multiple batches, one for each partition with data available to be sent.

    A small batch size will make batching less common and may reduce throughput (a batch size of zero will disable batching entirely). A very large batch size may use memory a bit more wastefully as we will always allocate a buffer of the specified batch size in anticipation of additional records. linger.msThe producer groups together any records that arrive in between request transmissions into a single batched request. Normally this occurs only under load when records arrive faster than they can be sent out. However in some circumstances the client may want to reduce the number of requests even under moderate load. This setting accomplishes this by adding a small amount of artificial delay—that is, rather than immediately sending out a record the producer will wait for up to the given delay to allow other records to be sent so that the sends can be batched together. This can be thought of as analogous to Nagle's algorithm in TCP. This setting gives the upper bound on the delay for batching: once we get batch.size worth of records for a partition it will be sent immediately regardless of this setting, however if we have fewer than this many bytes accumulated for this partition we will 'linger' for the specified time waiting for more records to show up. This setting defaults to 0 (i.e. no delay). Setting linger.ms=5, for example, would have the effect of reducing the number of requests sent but would add up to 5ms of latency to records sent in the absence of load.delivery.timeout.msAn upper bound on the time to report success or failure after a call to send() returns. This limits the total time that a record will be delayed prior to sending, the time to await acknowledgement from the broker (if expected), and the time allowed for retriable send failures. The producer may report failure to send a record earlier than this config if either an unrecoverable error is encountered, the retries have been exhausted, or the record is added to a batch which reached an earlier delivery expiration deadline. The value of this config should be greater than or equal to the sum of request.timeout.ms and linger.ms. client.idAn id string to pass to the server when making requests. The purpose of this is to be able to track the source of requests beyond just ip/port by allowing a logical application name to be included in server-side request logging.send.buffer.bytesvThe size of the TCP send buffer (SO_SNDBUF) to use when sending data. If the value is -1, the OS default will be used.receive.buffer.bytesyThe size of the TCP receive buffer (SO_RCVBUF) to use when reading data. If the value is -1, the OS default will be used.max.request.sizeDThe maximum size of a request in bytes. This setting will limit the number of record batches the producer will send in a single request to avoid sending huge requests. This is also effectively a cap on the maximum record batch size. Note that the server has its own cap on record batch size which may be different from this.reconnect.backoff.ms The base amount of time to wait before attempting to reconnect to a given host. This avoids repeatedly connecting to a host in a tight loop. This backoff applies to all connection attempts by the client to a broker.reconnect.backoff.max.msQThe maximum amount of time in milliseconds to wait when reconnecting to a broker that has repeatedly failed to connect. If provided, the backoff per host will increase exponentially for each consecutive connection failure, up to this maximum. After calculating the backoff increase, 20% random jitter is added to avoid connection storms.retry.backoff.msThe amount of time to wait before attempting to retry a failed request to a given topic partition. This avoids repeatedly sending requests in a tight loop under some failure scenarios. max.block.ms9The configuration controls how long KafkaProducer.send() and KafkaProducer.partitionsFor() will block.These methods can be blocked either because the buffer is full or metadata unavailable.Blocking in the user-supplied serializers or partitioner will not be counted against this timeout.request.timeout.msThe configuration controls the maximum amount of time the client will wait for the response of a request. If the response is not received before the timeout elapses the client will resend the request if necessary or fail the request if retries are exhausted. This should be larger than replica.lag.time.max.ms (a broker configuration) to reduce the possibility of message duplication due to unnecessary producer retries.metadata.max.age.msThe period of time in milliseconds after which we force a refresh of metadata even if we haven't seen any partition leadership changes to proactively discover any new brokers or partitions.metrics.sample.window.ms5The window of time a metrics sample is computed over.metrics.num.samples4The number of samples maintained to compute metrics.metrics.recording.level   (The highest recording level for metrics.metric.reportersA list of classes to use as metrics reporters. Implementing the org.apache.kafka.common.metrics.MetricsReporter interface allows plugging in classes that will be notified of new metric creation. The JmxReporter is always included to register JMX statistics.%max.in.flight.requests.per.connectionThe maximum number of unacknowledged requests the client will send on a single connection before blocking. Note that if this setting is set to be greater than 1 and there are failed sends, there is a risk of message re-ordering due to retries (i.e., if retries are enabled). uSerializer class for key that implements the org.apache.kafka.common.serialization.Serializer interface. wSerializer class for value that implements the org.apache.kafka.common.serialization.Serializer interface.connections.max.idle.msQClose idle connections after the number of milliseconds specified by this config.partitioner.class>org/apache/kafka/clients/producer/internals/DefaultPartitionerkPartitioner class that implements the org.apache.kafka.clients.producer.Partitioner interface.interceptor.classes1A list of classes to use as interceptors. Implementing the org.apache.kafka.clients.producer.ProducerInterceptor interface allows you to intercept (and possibly mutate) the records received by the producer before they are published to the Kafka cluster. By default, there are no interceptors.security.protocol PLAINTEXT   enable.idempotence  NWhen set to 'true', the producer will ensure that exactly one copy of each message is written in the stream. If 'false', producer retries due to broker failures, etc., may write duplicates of the retried message in the stream. Note that enabling idempotence requires max.in.flight.requests.per.connection to be less than or equal to 5, retries to be greater than 0 and acks must be 'all'. If these values are not explicitly set by the user, suitable values will be chosen. If incompatible values are set, a ConfigException will be thrown.transaction.timeout.msOThe maximum amount of time in ms that the transaction coordinator will wait for a transaction status update from the producer before proactively aborting the ongoing transaction.If this value is larger than the transaction.max.timeout.ms setting in the broker, the request will fail with a InvalidTransactionTimeout error.transactional.id7org/apache/kafka/common/config/ConfigDef$NonEmptyStringNonEmptyStringThe TransactionalId to use for transactional delivery. This enables reliability semantics which span multiple producer sessions since it allows the client to guarantee that transactions using the same TransactionalId have been completed prior to starting any new transactions. If no TransactionalId is provided, then the producer is limited to idempotent delivery. Note that enable.idempotence must be enabled if a TransactionalId is configured. The default is null, which means transactions cannot be used. Note that, by default, transactions require a cluster of at least three brokers which is the recommended setting for production; for development you can change this, by adjusting broker setting transaction.state.log.replication.factor.-org/apache/kafka/common/config/AbstractConfig java/util/Map"postProcessReconnectBackoffConfigsO(Lorg/apache/kafka/common/config/AbstractConfig;Ljava/util/Map;)Ljava/util/Map;java/lang/ObjectgetClass()Ljava/lang/Class;put8(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;putAlljava/lang/ClassgetName()Ljava/lang/String;<(Lorg/apache/kafka/common/config/ConfigDef;Ljava/util/Map;)V=(Lorg/apache/kafka/common/config/ConfigDef;Ljava/util/Map;Z)Vnamesjava/lang/SystemoutLjava/io/PrintStream; toHtmlTablejava/io/PrintStreamprintln(Ljava/lang/String;)V-org/apache/kafka/common/config/ConfigDef$TypeTypeLIST/Lorg/apache/kafka/common/config/ConfigDef$Type;java/util/Collections emptyList()Ljava/util/List;3org/apache/kafka/common/config/ConfigDef$Importance ImportanceHIGH5Lorg/apache/kafka/common/config/ConfigDef$Importance;define Validator(Ljava/lang/String;Lorg/apache/kafka/common/config/ConfigDef$Type;Ljava/lang/Object;Lorg/apache/kafka/common/config/ConfigDef$Validator;Lorg/apache/kafka/common/config/ConfigDef$Importance;Ljava/lang/String;)Lorg/apache/kafka/common/config/ConfigDef;LONGjava/lang/LongvalueOf(J)Ljava/lang/Long;.org/apache/kafka/common/config/ConfigDef$RangeRangeatLeastD(Ljava/lang/Number;)Lorg/apache/kafka/common/config/ConfigDef$Range;INT(I)Ljava/lang/Integer;betweenV(Ljava/lang/Number;Ljava/lang/Number;)Lorg/apache/kafka/common/config/ConfigDef$Range;STRING4org/apache/kafka/common/config/ConfigDef$ValidString ValidStringinK([Ljava/lang/String;)Lorg/apache/kafka/common/config/ConfigDef$ValidString;(Ljava/lang/String;Lorg/apache/kafka/common/config/ConfigDef$Type;Ljava/lang/Object;Lorg/apache/kafka/common/config/ConfigDef$Importance;Ljava/lang/String;)Lorg/apache/kafka/common/config/ConfigDef;MEDIUMLOW5org/apache/kafka/common/metrics/Sensor$RecordingLevelRecordingLevelINFO7Lorg/apache/kafka/common/metrics/Sensor$RecordingLevel;toStringDEBUGCLASS(Ljava/lang/String;Lorg/apache/kafka/common/config/ConfigDef$Type;Lorg/apache/kafka/common/config/ConfigDef$Importance;Ljava/lang/String;)Lorg/apache/kafka/common/config/ConfigDef;SECURITY_PROTOCOL_DOCwithClientSslSupport,()Lorg/apache/kafka/common/config/ConfigDef;withClientSaslSupportBOOLEANjava/lang/Boolean(Z)Ljava/lang/Boolean;2org/apache/kafka/common/config/ConfigDef$Validator&org/apache/kafka/common/metrics/Sensor!3ac;=.6>?_`@BCFILNOT\^ &X79dfhmop'-r tuxz{| L*+b  -Y*N+-+W,- ,W-g h ijk+l*--- $*--- $  3 Y N-* +-+ W,- , W-rs tuv#w1x*333+33 A *+ |} S *+    ^ *+         ;     YY !"$ $%&'(*++*+,-./01Y2SY3SY4SY0S567/89:;(@++%<=>(++%<?@(A++%<BC/D<E:F(G++%<HI(J++%<KL(M++%<NO!P$ $%RST!U$ $%RWX!Y$ $%R[\!]++%<^_(u0++%<`a!b++%Rcd!u0++%Ref(++%Rgh/ij1YijSYkjS5RlmYRno(++%Rpqrs qtsu!v+<w:xqy<z:{YR|}/~<:R:(]+R:/YR5&?u} "&1<Vp    )1%@#I+M,X)e/r3|:8=CAGLMPNUSX^B { @@   0 Y@