Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
Kafka >> mail # dev >> [jira] [Closed] (KAFKA-758) startHighWaterMarksCheckPointThread is never called


Copy link to this message
-
[jira] [Closed] (KAFKA-758) startHighWaterMarksCheckPointThread is never called

     [ https://issues.apache.org/jira/browse/KAFKA-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Neha Narkhede closed KAFKA-758.
-------------------------------

    
> startHighWaterMarksCheckPointThread is never called
> ---------------------------------------------------
>
>                 Key: KAFKA-758
>                 URL: https://issues.apache.org/jira/browse/KAFKA-758
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8
>            Reporter: Sriram Subramanian
>            Assignee: Sriram Subramanian
>            Priority: Blocker
>              Labels: p1
>             Fix For: 0.8
>
>         Attachments: KAFKA-758.patch
>
>
> startHighWaterMarksCheckPointThread is never called during startup and hence we only persist the highwater mark file on a clean shutdown. With an unclean shutdown, the highwater marks are not persisted. This causes long recovery time for replicas after unclean shutdowns.

--
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

 
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB