AFAIK not topics, but only partitions of topics have leaders. What controllers
do you mean? I haven't read about such.
Thanks for the explanation regarding the metadata request, in the meantime I
found out that this is an expected (!) failure
(http://qnalist.com/questions/4787268/kafka-common-l
You probably also want to check the request time jmx (in particular
FetchRequest time) on the broker to see if the broker is healthy.
Thanks,
Jun
On Fri, Sep 26, 2014 at 3:02 PM, Jagbir Hooda wrote:
> Hi Jun,
>
> Thanks for the info, we'll keep you posted on the above topic.
> Surprisingly in
Valentin,
That's a good point. We don't have this use case in mind when designing the
new consumer api. A straightforward implementation could be removing the
locally cached topic metadata for unsubscribed topics. It's probably
possible to add a config value to avoid churns in caching the metadata
It could be that broker 1 and 3 can't communicate with broker 2 and the
consumer client. You may want to read
https://cwiki.apache.org/confluence/display/KAFKA/FAQ#FAQ-Whycan'tmyconsumers/producersconnecttothebrokers
?
Thanks,
Jun
On Thu, Sep 25, 2014 at 1:52 PM, florent valdelievre <
florentval
