Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@minotaur.apache.org Received: (qmail 40011 invoked from network); 22 Feb 2010 18:41:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Feb 2010 18:41:33 -0000 Received: (qmail 16200 invoked by uid 500); 22 Feb 2010 18:41:33 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 16139 invoked by uid 500); 22 Feb 2010 18:41:33 -0000 Mailing-List: contact zookeeper-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: zookeeper-user@hadoop.apache.org Delivered-To: mailing list zookeeper-user@hadoop.apache.org Received: (qmail 16129 invoked by uid 99); 22 Feb 2010 18:41:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Feb 2010 18:41:33 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ted.dunning@gmail.com designates 209.85.222.188 as permitted sender) Received: from [209.85.222.188] (HELO mail-pz0-f188.google.com) (209.85.222.188) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Feb 2010 18:41:26 +0000 Received: by pzk26 with SMTP id 26so202649pzk.29 for ; Mon, 22 Feb 2010 10:41:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=MEfP/HXDCautAViA8bJGZ5ZNrMCjaWoGc8p1beHpaUk=; b=hTah6O6Q1hGQsYkMYJeXDSSeCLvcyo5tqoM1sW94P2jHy6KzruadmHQHHz0HLl1c9l D3+e/mWhKT6Yli6zn87xRAjER0YGzSrahiCkGjj+wa4nTL+fm+B6lcLgMIxdcXrH5cFZ J5IY9zlK6iqI+GPP7n0D7wjdifhHp6g8BcKkU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=d0c+nH3N2eocfVXVKYEPOuzqtWdK1DHC/6cBQowcEnbO2hLHtjvySw1+1sTqlNjIap u5tUkvwDp8iGBtIVplSHY7g4K445C16JliD4vLl2wLaF39VhhtTiJ1nforaqT/qN0KYG S8Y3gyOCznmiKZ1QvbeKbL/vNQDgmYCl1HuqA= MIME-Version: 1.0 Received: by 10.141.53.14 with SMTP id f14mr4078082rvk.266.1266864066077; Mon, 22 Feb 2010 10:41:06 -0800 (PST) In-Reply-To: <7c962aed1002221018j5d8b7e8ara29d37e07fe365b2@mail.gmail.com> References: <7c962aed1002221018j5d8b7e8ara29d37e07fe365b2@mail.gmail.com> From: Ted Dunning Date: Mon, 22 Feb 2010 10:40:46 -0800 Message-ID: Subject: Re: Bit of help debugging a TIMED OUT session please To: zookeeper-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=000e0cd29288a32606048034c6e1 --000e0cd29288a32606048034c6e1 Content-Type: text/plain; charset=UTF-8 Not sure this helps at all, but these times are remarkably asymmetrical. I would expect members of a ZK cluster to have very comparable times. Additionally, 345 ms is nowhere near large enough to cause a session to expire. My take is that ZK doesn't think it caused the timeout. On Mon, Feb 22, 2010 at 10:18 AM, Stack wrote: > Latency min/avg/max: 2/125/345 > ... > Latency min/avg/max: 0/7/81 > ... > Latency min/avg/max: 1/1/1 > > Thanks for any pointers on how to debug. > --000e0cd29288a32606048034c6e1--