Minor Description
As discussed with damianguy
streams clientId is set to applicationId-threadId-consumer which of course wouldn’t be unique if running multiple instances per host.
Example use case:
deployment as docker container on marathon so it might end up multiple times on the same host and of course they're all running with the same configuration. All clients on the same host would have the same clientid
Problem
Consumers running with the same client id make it hard to identify lagging consumers correctly
Potential solution:
Internally we do have a processId. It might make sense if we attached that to the clientId. it would then be unique across instances
Attachments
Issue Links
- duplicates
-
KAFKA-4117 Cleanup StreamPartitionAssignor behavior
-
- Resolved
-