Chris, First of all, thanks for running these tests and reporting the issues. We appreciate the help in testing Kafka 0.8.
> > First test: connect to a Broker that is a 'copy' of the topic/partition but > not leader. Get an error '5' which maps to > 'ErrorMapping.LeaderNotAvailableCode' Please can you file a JIRA for this ? Ideally, you should get back ErrorMapping.NotLeaderForPartitionCode. > > Knowing it was a clean shutdown would also allow me to treat the clean > shutdown as a normal occurrence vs. an exception when something goes wrong. > > Kafka handles controlled/clean shutdown by changing the leaders without introducing downtime for any partition. The expectation from the client is that you build the logic that will, on any failure, fetch the metadata and refetch the data. It actually doesn't matter if the connection was refused or if Kafka gives back an error code. Thanks, Neha
