Several of our search engines use pretty large heaps (12-24GB). That means
that if they *ever* do a full collection, disaster ensues because it can
take so long.
That means that we have to use concurrent collectors as much as possible and
make sure that the concurrent collectors get all the ephem
Can you elaborate on "gc tuning" - you are using the incremental collector?
Patrick
Ted Dunning wrote:
The server side is a fairly standard (but old) config:
tickTime=2000
dataDir=/home/zookeeper/
clientPort=2181
initLimit=5
syncLimit=2
Most of our clients now use 5 seconds as the timeout, bu
The server side is a fairly standard (but old) config:
tickTime=2000
dataDir=/home/zookeeper/
clientPort=2181
initLimit=5
syncLimit=2
Most of our clients now use 5 seconds as the timeout, but I think that we
went to longer timeouts in the past. Without digging in to determine the
truth of the ma
Ok, good. Based on the comparison of perf numbers, and Ted's experience
with large instances on ec2 running zk, this makes sense to me. A large
is about half (very roughly) the horsepower of what I was using for my
tests. Ted mentioned that he hasn't seen issues on ec2 running with
large instan
I only have one large instance live. My impression from previously is that
between host bandwidth is generally about what you saw. We have been able
to sustain 20-30MB/s into EC2 to a single node which should be harder than
moving data between nodes. I have heard rumors that others were able to
rked pretty well for me. We did extend all of our timeouts. The
biggest
worry for us was timeouts on the client side. The ZK server side was no
problem in that respect.
On Mon, Nov 9, 2009 at 4:20 PM, Jun Rao wrote:
Has anyone deployed ZK on EC2? What's the experience there? Are there
more
ti
>> biggest
>> worry for us was timeouts on the client side. The ZK server side was no
>> problem in that respect.
>>
>> On Mon, Nov 9, 2009 at 4:20 PM, Jun Rao wrote:
>>
>> Has anyone deployed ZK on EC2? What's the experience there? Are there
>>
outs. The biggest
worry for us was timeouts on the client side. The ZK server side was no
problem in that respect.
On Mon, Nov 9, 2009 at 4:20 PM, Jun Rao wrote:
Has anyone deployed ZK on EC2? What's the experience there? Are there more
timeouts, lead re-election, etc? Thanks,
Jun
IBM A
> jun...@almaden.ibm.com
>
>
> Ted Dunning wrote on 11/09/2009 04:24:16 PM:
>
> > [image removed]
> >
> > Re: ZK on EC2
> >
> > Ted Dunning
> >
> > to:
> >
> > zookeeper-user
> >
> > 11/09/2009 04:25 PM
> >
> > P
Thanks, Ted.
What long did you set the client timeout?
Jun
IBM Almaden Research Center
K55/B1, 650 Harry Road, San Jose, CA 95120-6099
jun...@almaden.ibm.com
Ted Dunning wrote on 11/09/2009 04:24:16 PM:
> [image removed]
>
> Re: ZK on EC2
>
> Ted Dunning
>
> to:
>
Worked pretty well for me. We did extend all of our timeouts. The biggest
worry for us was timeouts on the client side. The ZK server side was no
problem in that respect.
On Mon, Nov 9, 2009 at 4:20 PM, Jun Rao wrote:
> Has anyone deployed ZK on EC2? What's the experience there? A
Has anyone deployed ZK on EC2? What's the experience there? Are there more
timeouts, lead re-election, etc? Thanks,
Jun
IBM Almaden Research Center
K55/B1, 650 Harry Road, San Jose, CA 95120-6099
jun...@almaden.ibm.com
12 matches
Mail list logo