THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
FindCoordinator only allows to look up the coordinator for a single resource. For use cases working with several consumer groups, this forces to send one FindCoordinator request for each group. This can have a negative impact on performance.
This is the case with the following Admin APIs:
...
| Code Block | ||
|---|---|---|
| ||
{
"apiKey": 10,
"type": "request",
"name": "FindCoordinatorsRequest",
// Version 1 adds KeyType.
//
// Version 2 is the same as version 1.
//
// Version 3 is the first flexible version.
//
// Version 4 adds support for batching via CoordinatorKeys
"validVersions": "0-4",
"flexibleVersions": "3+",
"fields": [
{ "name": "Key", "type": "string", "versions": "0-3",
"about": "The coordinator key." },
{ "name": "KeyType", "type": "int8", "versions": "1+", "default": "0", "ignorable": false,
"about": "The coordinator key type. (Group, transaction, etc.)" },
{ "name": "CoordinatorKeys", "type": "[]string", "versions": "4+",
"about": "The coordinator keys." }
]
} |
...
| Code Block |
|---|
{
"apiKey": 10,
"type": "response",
"name": "FindCoordinatorsResponse",
// Version 1 adds throttle time and error messages.
//
// Starting in version 2, on quota violation, brokers send out responses before throttling.
//
// Version 3 is the first flexible version.
//
// Version 4 adds support for batching via Coordinators
"validVersions": "0-4",
"flexibleVersions": "3+",
"fields": [
{ "name": "ThrottleTimeMs", "type": "int32", "versions": "1+", "ignorable": true,
"about": "The duration in milliseconds for which the request was throttled due to a quota violation, or zero if the request did not violate any quota." },
{ "name": "ErrorCode", "type": "int16", "versions": "0-3",
"about": "The error code, or 0 if there was no error." },
{ "name": "ErrorMessage", "type": "string", "versions": "1-3", "nullableVersions": "1-3", "ignorable": true,
"about": "The error message, or null if there was no error." },
{ "name": "NodeId", "type": "int32", "versions": "0-3", "entityType": "brokerId",
"about": "The node id." },
{ "name": "Host", "type": "string", "versions": "0-3",
"about": "The host name." },
{ "name": "Port", "type": "int32", "versions": "0-3",
"about": "The port." },
{ "name": "Coordinators", "type": "[]Coordinator", "versions": "4+", "about": "Each coordinator result in the response", "fields": [
{ "name": "Key", "type": "string", "versions": "4+", "about": "The coordinator key." },
{ "name": "NodeId", "type": "int32", "versions": "4+", "entityType": "brokerId",
"about": "The node id." },
{ "name": "Host", "type": "string", "versions": "4+", "about": "The host name." },
{ "name": "Port", "type": "int32", "versions": "4+", "about": "The port." },
{ "name": "ErrorCode", "type": "int16", "versions": "4+",
"about": "The error code, or 0 if there was no error." },
{ "name": "ErrorMessage", "type": "string", "versions": "4+", "nullableVersions": "4+", "ignorable": true,
"about": "The error message, or null if there was no error." }
]}
]
} |
Proposed Changes
We'll update KafkaConsumer, KafkaProducer and KafkaAdminClient will be updated to use the new version of FindCoordinators. If brokers don't support v4, KafkaConsumer, KafkaProducer and KafkaAdminClient clients will automatically revert to the old behaviour.
We'll update KafkaAdminClient to resolve KafkaAdminClient will be updated to find all group coordinators in a single call if possible for both deleteConsumerGroups() and describeConsumerGroups().
Compatibility, Deprecation, and Migration Plan
If this feature is not supported by brokers, clients will automatically revert to the old behaviour. There are no public API changes.
Rejected Alternatives
None