THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| config | Consumer behavior | AdminClient behavior | Description | |||
|---|---|---|---|---|---|---|
client.dns.lookup, bootstrap.servers | use ClientUtils.parseAndValidateAddresses to get InetSocketAddress of broker, and to sendMedatataRequest to the broker. | use ClientUtils.parseAndValidateAddresses to get InetSocketAddress of broker, and to send MedatataRequest to the broker. | Both clients will take same action | |||
| default.api.timeout.ms | The consumer will retry until the timeout is reached | The AdminClient will retry until the timeout is reached or the number of retries exceeds the limit | AdminClient does the same with Consumer since the default of `retries` is In Integer.MaxValue and have the same default timeout value | |||
| sessionrequest.timeout.ms | Only used in ConsumerCoordinator | not used | have no effect to remove this config | Used by NetworkClient for individual rpcs to await acknowledgment from servers | Used by KafkaAdminClient to decide whether each and the timeout for NetworkClient is 3600000 | There is a small difference wheras the result are the same. |
send.buffer.bytes, receive.buffer.bytes, | Used to construct NetworkClient | Used to construct NetworkClient | Both clients will take same action | |||
The amount of time to wait before attempting to retry a failed ListOffsetsRequest rpc and MetadataRequest rpc | The amount of time to wait before attempting to retry a failed ListOffsetsRequest rpc and MetadataRequest rpc | Both clients will take same action | ||||
| just an identifier | have no impact | |||||
The period of time to evict metadata cache for `ConsumerMetadata` | The period of time to evict metadata cache for `AdminMetadataManager` | There may be difference in implementation details, the metadata cache will have the same expire time. | ||||
metric.reporters, and all other metric releated configs | Used to get client metrics | Used to get client metrics | have no impact | |||
security.protocol, and all other security related configs | Used to establish security connection | Used to establish security connection | Both clients will take same action | |||
| retries | Consumer will retries until default.api.timeout.ms is reached | default value is Integer.MaxValue | The AdminClient will act the same with Consumer by default, and we can set a config to control how many times we can retry | request.timeout.ms | This is used when getting end offsets, I think this is a impletion gap of KIP-266 and should be fixed by using default.api.timeout.ms | Will use default.api.timeout.ms instead of request.timeout.ms , This is a small bug and will be fixed in a separate PR |
So we can conclude this is a compatible change and the transition won't be noticed.
...