[
https://issues.apache.org/jira/browse/KAFKA-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133580#comment-15133580
]
TAO XIAO commented on KAFKA-3206:
---------------------------------
This is most likely due to unclean.leader.election.enable being set to true. It
basically means any out of sync node can take over leadership and receive
traffic. If you have unclean.leader.election.enable turned off the node you
brought up in step 4 will not become a leader therefore no more messages can be
sent to this partition.
> No reconsiliation after partitioning
> ------------------------------------
>
> Key: KAFKA-3206
> URL: https://issues.apache.org/jira/browse/KAFKA-3206
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.9.0.0
> Reporter: Arkadiusz Firus
>
> Kafka topic partition could be in an inconsistent state where two nodes see
> different partition state.
> Steps to reproduce the problem:
> 1. Create topic with one partition and replication factor 2
> 2. Stop one of the Kafka nodes where that partition resides
> 3. Send following messages to that topic:
> ABC
> BCD
> CDE
> 3. Stop the other Kafka node
> Currently none of the nodes should be running
> 4. Start first Kafka node - this node has no records
> 5. Send following records to the topic:
> 123
> 234
> 345
> 6. Start the other Kafka node
> The reconciliation should happen here but it does not.
> 7. When you read the topic you will see
> 123
> 234
> 345
> 8. When you stop the first node and read the topic you will see
> ABC
> BCD
> CDE
> This means that the partition is in inconsistent state.
> If you have any questions please feel free to e-mail me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
