Mailing-List: contact zookeeper-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: zookeeper-user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of timrobertson100@gmail.com
 designates 209.85.215.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=nJBct7x+R1kKs3bKul3gHOgx/DIGOheOeqOJnEFpfWT6A22neL1+HFbSMel23oyO1O
         2H422DRRY6gRld679sgNB4SF07i3pLs7njDdBZcZAADoNkQW4Dvu3AMrb0aKFWFwF3Ec
         H1QRlPq+53u6E7RgZdN91lA8OkIYGJ0asfwhw=
MIME-Version: 1.0
Date: Tue, 21 Sep 2010 17:24:29 +0200
Message-ID: <AANLkTimWPV-e6o0YAto33BqHygiJaaTG10twW8yQojzB@mail.gmail.com>
Subject: Expiring session... timeout of 600000ms exceeded
From: Tim Robertson <timrobertson100@gmail.com>
To: zookeeper-user@hadoop.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

I am seeing a lot of my clients being kicked out after the 10 minute
negotiated timeout is exceeded.
My clients are each a JVM (around 100 running on a machine) which are
doing web crawling of specific endpoints and handling the response XML
- so they do wait around for 3-4 minutes on HTTP timeouts, but
certainly not 10 mins.
I am just prototyping right now on a 2xquad core mac pro with 12GB
memory, and the 100 child processes only get -Xmx64m and I don't see
my machine exhausted.

Do my clients need to do anything in order to initiate keep alive
heart beats or should this be automatic (I thought the ticktime would
dictate this)?

# my conf is:
tickTime=2000
dataDir=/Volumes/Data/zookeeper
clientPort=2181
maxClientCnxns=10000
minSessionTimeout=4000
maxSessionTimeout=800000

Thanks for any pointers to this newbie,
Tim