You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2014/07/21 18:14:39 UTC

[jira] [Commented] (KAFKA-1553) TopicMetadataResponse.brokers not read in scala producer?

    [ https://issues.apache.org/jira/browse/KAFKA-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068708#comment-14068708 ] 

Jun Rao commented on KAFKA-1553:
--------------------------------

Yes, that's the behavior of the old producer. We are changing that behavior in the new producer.

> TopicMetadataResponse.brokers not read in scala producer?
> ---------------------------------------------------------
>
>                 Key: KAFKA-1553
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1553
>             Project: Kafka
>          Issue Type: Bug
>          Components: producer 
>    Affects Versions: 0.8.2
>            Reporter: Nicolae Marasoiu
>            Assignee: Jun Rao
>
> I searched again and I do think that topicMetadataResponse.brokers is not read in Scala Producer, or I have not found where it is. (In the java producer it does seem used on the other hand).
> The producer seems to only parse its static configuration (properties file on key metadata.broker.list on disk stating initial broker list), and cache it in BrokerPartitionInfo. It never updates that broker list cache when it receives a metadata response!
> It really seems that only that statically configured metadata.broker.list is ever queried for metadata, not only initially but at any time e.g. this list is never refreshed with the brokers listed in the topic metadata response.



--
This message was sent by Atlassian JIRA
(v6.2#6252)