From dev-return-69253-archive-asf-public=cust-asf.ponee.io@zookeeper.apache.org Wed Apr 25 23:46:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 98E34180676 for ; Wed, 25 Apr 2018 23:46:04 +0200 (CEST) Received: (qmail 90190 invoked by uid 500); 25 Apr 2018 21:46:03 -0000 Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zookeeper.apache.org Delivered-To: mailing list dev@zookeeper.apache.org Received: (qmail 90179 invoked by uid 99); 25 Apr 2018 21:46:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Apr 2018 21:46:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 1CFDBC006A for ; Wed, 25 Apr 2018 21:46:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Yti5TFiHrmPo for ; Wed, 25 Apr 2018 21:46:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 368045FBF7 for ; Wed, 25 Apr 2018 21:46:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 492C7E1277 for ; Wed, 25 Apr 2018 21:46:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 9826F241E6 for ; Wed, 25 Apr 2018 21:46:00 +0000 (UTC) Date: Wed, 25 Apr 2018 21:46:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@zookeeper.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ZOOKEEPER-2994) Tool required to recover log and snapshot entries with CRC errors MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ZOOKEEPER-2994?page=3Dcom.atlas= sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D= 16453134#comment-16453134 ]=20 ASF GitHub Bot commented on ZOOKEEPER-2994: ------------------------------------------- Github user phunt commented on the issue: https://github.com/apache/zookeeper/pull/508 =20 +1. Great. Thanks @anmolnar . I've committed for 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 corrupt= ed and fail CRC checks (preventing startup) we should have a mechanism to g= et the cluster running again. > Previously=C2=A0we achieved this by loading the broken transaction log wi= th a modified version of ZK with disabled CRC check and forced it to snapsh= ot. > 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 file= s, it'd be nice to extend their functionality and add ability for such reco= very. > It has proven that once you end up with the corrupt txn log there is no w= ay 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)