[
https://issues.apache.org/jira/browse/KAFKA-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede resolved KAFKA-423.
---------------------------------
Resolution: Not A Problem
This is not a bug in the current code since KafkaZookeeper starts up before
ReplicaManager and bootstraps all local replicas before ReplicaManager
schedules the highwatermark checkpoint thread.
> On startup, highwatermark file should be written to only after all local
> replicas have been started
> ---------------------------------------------------------------------------------------------------
>
> Key: KAFKA-423
> URL: https://issues.apache.org/jira/browse/KAFKA-423
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: Neha Narkhede
> Assignee: Neha Narkhede
>
> On startup, the replica manager starts local replicas for all partitions on
> disk. At the same time, it also schedules the highwatermark checkpoint
> thread. The thread takes the in-memory local replica data structure and
> writes the highwatermark values for each of those to disk. However, the
> replica manager should checkpoint data only after the internal local replica
> data structures are populated or else the highwatermark file can end up being
> overwritten with empty or fewer values.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
