[
https://issues.apache.org/jira/browse/KAFKA-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132862#comment-15132862
]
Vahid Hashemian commented on KAFKA-3206:
----------------------------------------
I can reproduce this issue. It looks like after step 6 the two brokers are
sync'ed only on their partition offsets, and not the actual messages received.
> 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)
