Overall the 0.8.2.0 release candidate looks really good. All of the kafka-python integration tests pass as they do w/ prior servers, except one... When testing recovery from a broker failure / leader switch, we now see a ReplicaNotAvailableError in broker metadata / PartitionMetadata, which we do not see in the same test against previous servers. I understand from discussion around KAFKA-1609 and KAFKA-1649 that this behavior is expected and that clients should ignore the error (or at least treat it as non-critical). But strictly speaking this is a behavior change and could cause client issues. Indeed, anyone using older versions of kafka-python against this release candidate will get bad failures on leader switch (exactly when you don't want bad client failures!). It may be that it is our fault for not handling this in kafka-python, but at the least I think this needs to be flagged as a possible issue for 3rd party clients. Also KAFKA-1649 doesn't look like it was ever actually resolved... The protocol document does not mention anything about clients ignoring this error code.
Dana Powers Rdio, Inc. dana.pow...@rd.io rdio.com/people/dpkp/
