Sriram Subramanian created KAFKA-769:
----------------------------------------
Summary: On startup, a brokers highwatermark for every topic
partition gets reset to zero
Key: KAFKA-769
URL: https://issues.apache.org/jira/browse/KAFKA-769
Project: Kafka
Issue Type: Bug
Affects Versions: 0.8
Reporter: Sriram Subramanian
Assignee: Sriram Subramanian
Priority: Blocker
Fix For: 0.8
There is a race condition between the highwatermark thread and the
handleLeaderAndIsrRequest call of the request handler thread. When a broker
starts, the highwatermark thread tries to persist all the checkpoints of the
partitions in ReplicaManager. This partition map in ReplicaManager is initially
empty. When the leaderAndIsrRequest runs, it updates each partition and if the
highwatermark thread runs during this interval, it is essentially going to
overwrite the highwatermark file to an inconsistent state. The read of the
highwatermark reads from the file each time and hence would return the
inconsistent state.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
