4             logLorg/slf4j/Logger;BOOTSTRAP_SERVERS_CONFIGLjava/lang/String; ConstantValueBOOTSTRAP_SERVERS_DOCCLIENT_DNS_LOOKUP_CONFIGCLIENT_DNS_LOOKUP_DOCMETADATA_MAX_AGE_CONFIGMETADATA_MAX_AGE_DOCSEND_BUFFER_CONFIGSEND_BUFFER_DOCSEND_BUFFER_LOWER_BOUNDIRECEIVE_BUFFER_CONFIGRECEIVE_BUFFER_DOCRECEIVE_BUFFER_LOWER_BOUNDCLIENT_ID_CONFIG CLIENT_ID_DOCCLIENT_RACK_CONFIGCLIENT_RACK_DOCRECONNECT_BACKOFF_MS_CONFIGRECONNECT_BACKOFF_MS_DOCRECONNECT_BACKOFF_MAX_MS_CONFIGRECONNECT_BACKOFF_MAX_MS_DOCRETRIES_CONFIG RETRIES_DOCRETRY_BACKOFF_MS_CONFIGRETRY_BACKOFF_MS_DOCMETRICS_SAMPLE_WINDOW_MS_CONFIGMETRICS_SAMPLE_WINDOW_MS_DOCMETRICS_NUM_SAMPLES_CONFIGMETRICS_NUM_SAMPLES_DOCMETRICS_RECORDING_LEVEL_CONFIGMETRICS_RECORDING_LEVEL_DOCMETRIC_REPORTER_CLASSES_CONFIGMETRIC_REPORTER_CLASSES_DOCSECURITY_PROTOCOL_CONFIGSECURITY_PROTOCOL_DOCDEFAULT_SECURITY_PROTOCOLCONNECTIONS_MAX_IDLE_MS_CONFIGCONNECTIONS_MAX_IDLE_MS_DOCREQUEST_TIMEOUT_MS_CONFIGREQUEST_TIMEOUT_MS_DOCGROUP_ID_CONFIG GROUP_ID_DOCGROUP_INSTANCE_ID_CONFIGGROUP_INSTANCE_ID_DOCMAX_POLL_INTERVAL_MS_CONFIGMAX_POLL_INTERVAL_MS_DOCREBALANCE_TIMEOUT_MS_CONFIGREBALANCE_TIMEOUT_MS_DOCSESSION_TIMEOUT_MS_CONFIGSESSION_TIMEOUT_MS_DOCHEARTBEAT_INTERVAL_MS_CONFIGHEARTBEAT_INTERVAL_MS_DOC()VCodeLineNumberTableLocalVariableTablethis.Lorg/apache/kafka/clients/CommonClientConfigs;"postProcessReconnectBackoffConfigsO(Lorg/apache/kafka/common/config/AbstractConfig;Ljava/util/Map;)Ljava/util/Map;config/Lorg/apache/kafka/common/config/AbstractConfig; parsedValuesLjava/util/Map;rvalLjava/util/HashMap;LocalVariableTypeTable5Ljava/util/Map;9Ljava/util/HashMap; StackMapTable Signature(Lorg/apache/kafka/common/config/AbstractConfig;Ljava/util/Map;)Ljava/util/Map; SourceFileCommonClientConfigs.java java/util/HashMap ,org/apache/kafka/clients/CommonClientConfigsreconnect.backoff.max.ms reconnect.backoff.ms IDisabling exponential reconnect backoff because {} is set, but {} is not.  java/lang/StringBuilder=Protocol used to communicate with brokers. Valid values are:  ,  . ^java/lang/Objectbootstrap.serversdA 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).client.dns.lookupControls how the client uses DNS lookups. If set to use_all_dns_ips then, when the lookup returns multiple IP addresses for a hostname, they will all be attempted to connect to before failing the connection. Applies to both bootstrap and advertised servers. If the value is resolve_canonical_bootstrap_servers_only each entry will be resolved and expanded into a list of canonical names.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.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. 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. client.rackA rack identifier for this client. This can be any string value which indicates where this client is physically located. It corresponds with the broker config 'broker.rack'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.QThe 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.retries|Setting a value greater than zero will cause the client to resend any request that fails with a potentially transient error.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.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.security.protocol PLAINTEXTconnections.max.idle.msQClose idle connections after the number of milliseconds specified by this config.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.group.idA unique string that identifies the consumer group this consumer belongs to. This property is required if the consumer uses either the group management functionality by using subscribe(topic) or the Kafka-based offset management strategy.group.instance.idA unique identifier of the consumer instance provided by the end user. Only non-empty strings are permitted. If set, the consumer is treated as a static member, which means that only one instance with this ID is allowed in the consumer group at any time. This can be used in combination with a larger session timeout to avoid group rebalances caused by transient unavailability (e.g. process restarts). If not set, the consumer will join the group as a dynamic member, which is the traditional behavior.max.poll.interval.msThe maximum delay between invocations of poll() when using consumer group management. This places an upper bound on the amount of time that the consumer can be idle before fetching more records. If poll() is not called before expiration of this timeout, then the consumer is considered failed and the group will rebalance in order to reassign the partitions to another member. For consumers using a non-null group.instance.id which reach this timeout, partitions will not be immediately reassigned. Instead, the consumer will stop sending heartbeats and partitions will be reassigned after expiration of session.timeout.ms. This mirrors the behavior of a static consumer which has shutdown.rebalance.timeout.ms>The maximum allowed time for each worker to join the group once a rebalance has begun. This is basically a limit on the amount of time needed for all tasks to flush any pending data and commit offsets. If the timeout is exceeded, then the worker will be removed from the group, which will cause offset commit failures.session.timeout.ms The timeout used to detect client failures when using Kafka's group management facility. The client sends periodic heartbeats to indicate its liveness to the broker. If no heartbeats are received by the broker before the expiration of this session timeout, then the broker will remove this client from the group and initiate a rebalance. Note that the value must be in the allowable range as configured in the broker configuration by group.min.session.timeout.ms and group.max.session.timeout.ms.heartbeat.interval.msThe expected time between heartbeats to the consumer coordinator when using Kafka's group management facilities. Heartbeats are used to ensure that the consumer's session stays active and to facilitate rebalancing when new consumers join or leave the group. The value must be set lower than session.timeout.ms, but typically should be set no higher than 1/3 of that value. It can be adjusted even lower to control the expected time for normal rebalances.-org/apache/kafka/common/config/AbstractConfig originals()Ljava/util/Map; java/util/Map containsKey(Ljava/lang/Object;)Zorg/slf4j/Loggerdebug9(Ljava/lang/String;Ljava/lang/Object;Ljava/lang/Object;)Vget&(Ljava/lang/Object;)Ljava/lang/Object;put8(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;org/slf4j/LoggerFactory getLogger%(Ljava/lang/Class;)Lorg/slf4j/Logger;append-(Ljava/lang/String;)Ljava/lang/StringBuilder;6org/apache/kafka/common/security/auth/SecurityProtocolnames()Ljava/util/List;#org/apache/kafka/common/utils/Utilsjoin<(Ljava/util/Collection;Ljava/lang/String;)Ljava/lang/String;toString()Ljava/lang/String;!4 !"#$%&'()*+,-./012345/06789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~/*  CYM*.*   ,+  W,$2A CC;C;AO+ Y [\*[