[ https://issues.apache.org/jira/browse/ZOOKEEPER-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-2994: ------------------------------------ Affects Version/s: 3.4.13 > Tool required to recover log and snapshot entries with CRC errors > ----------------------------------------------------------------- > > Key: ZOOKEEPER-2994 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2994 > Project: ZooKeeper > Issue Type: New Feature > Affects Versions: 3.5.4, 3.6.0, 3.4.13 > Reporter: Andor Molnar > Assignee: Andor Molnar > Priority: Major > Fix For: 3.5.4, 3.6.0, 3.4.13 > > > In the even that the zookeeper transaction log or snapshot become corrupted > and fail CRC checks (preventing startup) we should have a mechanism to get > the cluster running again. > Previously we achieved this by loading the broken transaction log with a > modified version of ZK with disabled CRC check and forced it to snapshot. > It'd very handy to have a tool which can do this for us. LogFormatter and > SnapshotFormatter have already been designed to dump log and snapshot files, > it'd be nice to extend their functionality and add ability for such recovery. > It has proven that once you end up with the corrupt txn log there is no way > to recover except manually modifying the crc check. That's basically why the > tool is needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)