[
https://issues.apache.org/jira/browse/KAFKA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280724#comment-14280724
]
Jun Rao commented on KAFKA-1649:
--------------------------------
This is discussed in the mailing list. The behavior already exists in 0.8.1. It
occurs less frequently than 0.8.2, but can still happen. To reproduce that
behavior in 0.8.1, you can do the following: (1) start 2 brokers, (2) create a
topic with 1 partition and 2 replicas, (3) bring down both brokers, (4) restart
only 1 broker, (5) issue a TopicMetadataRequest on that topic, (6) you should
see the ReplicaNotAvailableError code.
> Protocol documentation does not indicate that ReplicaNotAvailable can be
> ignored
> --------------------------------------------------------------------------------
>
> Key: KAFKA-1649
> URL: https://issues.apache.org/jira/browse/KAFKA-1649
> Project: Kafka
> Issue Type: Improvement
> Components: website
> Affects Versions: 0.8.1.1
> Reporter: Hernan Rivas Inaka
> Priority: Minor
> Labels: protocol-documentation
> Original Estimate: 10m
> Remaining Estimate: 10m
>
> The protocol documentation here
> https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol-ErrorCodes
> should indicate that error 9 (ReplicaNotAvailable) can be safely ignored on
> producers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
