[
https://issues.apache.org/jira/browse/KAFKA-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207568#comment-15207568
]
ASF GitHub Bot commented on KAFKA-3447:
---
GitHub user ijuma opened a pull request:
https://github.com/apache/kafka/pull/1117
KAFKA-3447; partitionState in UpdateMetadataRequest not logged properly
state-change log
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ijuma/kafka kafka-3447-metadata-cache-logging
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1117.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1117
> partitionState in UpdateMetadataRequest not logged properly state-change log
>
>
> Key: KAFKA-3447
> URL: https://issues.apache.org/jira/browse/KAFKA-3447
> Project: Kafka
> Issue Type: Improvement
>Affects Versions: 0.10.0.0
>Reporter: Jun Rao
>Assignee: Ismael Juma
>
> Saw the following in state-change log. The following logging comes from
> MetadataCache.updateCache().
> TRACE Broker 0 cached leader info
> org.apache.kafka.common.requests.UpdateMetadataRequest$PartitionState@6fc2c671
> for partition test-0 in response to UpdateMetadata request sent by
> controller 0 epoch 1 with correlation id 3 (state.change.logger)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
