Return-Path: X-Original-To: apmail-zookeeper-user-archive@www.apache.org Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CBE90FF89 for ; Mon, 25 Mar 2013 19:54:08 +0000 (UTC) Received: (qmail 6650 invoked by uid 500); 25 Mar 2013 19:54:07 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 6575 invoked by uid 500); 25 Mar 2013 19:54:07 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 6564 invoked by uid 99); 25 Mar 2013 19:54:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Mar 2013 19:54:07 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of briantarbox@gmail.com designates 209.85.215.44 as permitted sender) Received: from [209.85.215.44] (HELO mail-la0-f44.google.com) (209.85.215.44) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Mar 2013 19:54:01 +0000 Received: by mail-la0-f44.google.com with SMTP id eb20so12182569lab.3 for ; Mon, 25 Mar 2013 12:53:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=Cy6JMsrRmVVlovjlRJd5Yuro/byTYNce6gpY5tuyU+8=; b=qtVwP0+vFEPCAVX0Ztyz2oz63HfK3FS9kKCOmBwk+TFPbsmNfyeB5RcOjgHBsrRQWq mP14OmWLaVt6DBqdUmGPBUpZZB+pRf/nHONqJag4QxqFpi0rqnySwoAEOM2GkfQcmWzs ss4C9nuKVxnm3Ob7opPyvi8O/cMibrnau+qDjkSVDWRB5v9CZBLQwdu6SYhJuZuiXZTp TheZaE2KJwYYzULNnJKC8GGO//cVXGScEstmr6UORJPsz/hd3s533SnGJVBvhW2RuCL+ MvIgjWyMBWwsKmuE7N+hfaaQQdpOUn4UDSKEHDF8Tom09xmY5ekif2LgOMfp0AiSM445 SfUQ== MIME-Version: 1.0 X-Received: by 10.112.5.6 with SMTP id o6mr6679635lbo.57.1364241220919; Mon, 25 Mar 2013 12:53:40 -0700 (PDT) Received: by 10.112.24.136 with HTTP; Mon, 25 Mar 2013 12:53:40 -0700 (PDT) Date: Mon, 25 Mar 2013 15:53:40 -0400 Message-ID: Subject: how do you examine the transaction log? From: Brian Tarbox To: user@zookeeper.apache.org Content-Type: multipart/alternative; boundary=14dae94ee2535c67cd04d8c5297a X-Virus-Checked: Checked by ClamAV on apache.org --14dae94ee2535c67cd04d8c5297a Content-Type: text/plain; charset=ISO-8859-1 I'm running on Amazon's EC2 and "sometimes" find myself with ephemeral nodes after all of my workers have exited or been terminated. I've seen other reports of this problem that turned out to be user error after one of the Zookeeper maintainers dumped the transaction log and found a problem. (See Jira issue ZOOKEEPER-1600) I'd love to solve this problem myself but the transaction log looks binary to me. I see references to my nodes and paths but any actions look binary. Is there a way to decipher the log? Thanks. -- http://about.me/BrianTarbox --14dae94ee2535c67cd04d8c5297a--