using docker volumes results in 'NotLeaderForPartitionException' about kafka-docker

[splix]

Have exactly same issue with Docker volumes.

On producer side:

Failed to send producer request with correlation id 13 to broker 1 with data for partitions [test,1]

On consumer side:

kafka.common.NotLeaderForPartitionException

Works fine if internal FS is used. I believe it's a Kafka issue, maybe some incompatibility with Docker NFS

[wurstmeister]

Hi,

I can't reproduce this problem.

could you please share:

• your environment (boot2docker, native linux)
• your full fig.yml
• exact steps you've taken before you got this error (incl topic creation, restarts, etc)

could you also share the output of $KAFKA_HOME/bin/kafka-topics.sh --describe --topic perftest --zookeeper $ZK

Also just to ensure it's not caused by random port assignments (#27) could you please check if you can get it to work with https://github.com/wurstmeister/kafka-docker/blob/master/fig-single-broker.yml as your base configuration?

Thanks

[mavencode01]

I upgraded my docker to 1.5.0 and am wondering if this could be cause of the error

[2015-04-11 21:46:17,543] WARN Error while fetching metadata [{TopicMetadata for topic topic ->
No partition metadata for topic topic due to kafka.common.LeaderNotAvailableException}] for topic [topic]: class kafka.common.LeaderNotAvailableException

I found the problem, the KAFKA_ADVERTISED_HOST_NAME I used was wrong IP.

Thanks!

[sscaling]

Closing due to staleness. Not had any recent complaints of this issue.