gc pressure), etc...)
Patrick
Satish Bhatti wrote:
Session timeout is 30 seconds.
On Tue, Sep 1, 2009 at 4:26 PM, Patrick Hunt ph...@apache.org wrote:
What is your client timeout? It may be too low.
also see this section on handling recoverable errors:
http://wiki.apache.org/hadoop
is the second client doing?
On Tue, Jun 2, 2009 at 1:49 PM, Satish Bhatti cthd2...@gmail.com wrote:
stat
Zookeeper version: 3.1.1-755636, built on 03/18/2009 16:52 GMT
Clients:
/127.0.0.1:42460[1](queued=0,recved=0,sent=0)
/172.16.0.178:34283[1](queued=0,recved=925109,sent=925109
that we can release it to the
community.
On Tue, May 26, 2009 at 4:22 PM, Satish Bhatti cthd2...@gmail.com
wrote:
Does anybody have a utility to view a ZooKeeper cluster? Something like
a
file tree viewer?
Satish
--
Ted Dunning, CTO
DeepDyve
--
Ted Dunning, CTO
Here is the scenario:
(1) We have 2 live instances of our application, running on 2 different sets
of machines, a preproduction instance and a production instance. As part of
this setup we have 5 ZooKeeper servers running on machines pre-1 thru pre-5.
They have been running for several days.
bits) and child (32 bits)) would form a long.
I don't think this should be very hard to implement. Their is nothing in
zookeeper (out of the box) currently that would help you out.
Mahadev
On 4/23/09 4:52 PM, Satish Bhatti cthd2...@gmail.com wrote:
We currently use a database sequence
with that approach, but you should be able to generate millions of
guaranteed unique id's per second and these id's should be pretty dense if
each process generates lots of id's.
On Thu, Apr 23, 2009 at 4:52 PM, Satish Bhatti cthd2...@gmail.com wrote:
We currently use a database sequence
. With (c),
you
could have potentially large gaps in the sequence, but 64 bits that
shouldn't be a big deal. Code for that version would be the simplest of
any
of them.
On Fri, Apr 24, 2009 at 8:56 AM, Satish Bhatti cthd2...@gmail.com wrote:
Hello Ben,
Basically the ids are document Ids. We
