Description
When we issue an metadatarequest towards the cluster, the list of brokers is stale. I mean, even when a broker is down, it's returned back to the client. The following are examples of two invocations one with both brokers online and the second with a broker down:
{
"brokers": [
,
{ "nodeId": 1, "host": "localhost", "port": 9093, "byteLength": 19 } ],
"topicMetadata": [
{
"topicErrorCode": 0,
"topicName": "foozbar",
"partitions": [
,
,
,
,
{ "replicas": [ 0 ], "isr": [ 0 ], "partitionErrorCode": 0, "partitionId": 4, "leader": 0, "byteLength": 26 } ],
"byteLength": 145
}
],
"responseSize": 200,
"correlationId": -1000
}
{
"brokers": [
,
{ "nodeId": 1, "host": "localhost", "port": 9093, "byteLength": 19 } ],
"topicMetadata": [
{
"topicErrorCode": 0,
"topicName": "foozbar",
"partitions": [
,
,
,
,
{ "replicas": [ 0 ], "isr": [], "partitionErrorCode": 5, "partitionId": 4, "leader": -1, "byteLength": 22 } ],
"byteLength": 133
}
],
"responseSize": 188,
"correlationId": -1000
}
Attachments
Attachments
Issue Links
- is related to
-
KAFKA-1367 Broker topic metadata not kept in sync with ZooKeeper
- Resolved