Yes - the watchers aren't simply relay objects, they typically actually
process the callback.
Scaling out the watchers in a single client is a laudable aim, but I think
this proposal would impact some common use cases.
Henry
On 18 March 2010 15:47, Ted Dunning wrote:
> This kind of sounds stra
This kind of sounds strange to me.
My typical idiom is to create a watcher but not retain any references to it
outside the client. It sounds to me like your change will cause my watchers
to be collected and deactivated when GC happens.
On Thu, Mar 18, 2010 at 3:32 AM, Dominic Williams <
thedwill
Thanks to you for figuring out that it was a problem (and for having a new
and strange environment to test ZK in!)
On Thu, Mar 18, 2010 at 1:36 PM, Łukasz Osipiuk wrote:
> That is great. Thank you very much for your work!
Hi!
On Thu, Mar 18, 2010 at 21:23, Patrick Hunt wrote:
> We've identified the problem and are working on a fix. Full details here:
>
> https://issues.apache.org/jira/browse/ZOOKEEPER-710
>
That is great. Thank you very much for your work!
All the best, Łukasz
> Patrick
>
> Łukasz Osipiuk wr
We've identified the problem and are working on a fix. Full details here:
https://issues.apache.org/jira/browse/ZOOKEEPER-710
Patrick
Łukasz Osipiuk wrote:
Hello Mahadev,
2010/3/18 Mahadev Konar :
Hi Lukasz,
I looked at the logs and havent been able to determine how the session
move can hap
yes it means in sync with the leader. syncLimit governs the timeout when
a follower is actively following a leader. initLimit is the initial
connection timeout. because there is the potential for more data that
needs to be transmitted during the initial connection, we want to be
able to manage
Hi all,
I'm would like to get a better understanding of "syncLimit" configuration
property.
Accordingly to Administration Guide: "Amount of time, in ticks (see
tickTime),
to allow followers to sync with ZooKeeper. If followers fall too far behind
a leader, they will be dropped."
"...to sync with
we have updated ZOOKEEPER-713 with much more detail, but the bottom line
is that the Invalid snapshot was caused by an OutOfMemoryError. this
turns out not be a problem since we recover using an older snapshot.
there are other things that are happening that are the real causes of
the problem. s
Hi guys,
Today we experienced another problem with our zookeeper installation.
Due to large attachments I created jira issue for it, even though it
is rather question than bug report.
https://issues.apache.org/jira/browse/ZOOKEEPER-713
Description below:
Today we had major failure in our produc
Hello Mahadev,
2010/3/18 Mahadev Konar :
> Hi Lukasz,
> I looked at the logs and havent been able to determine how the session
> move can happen.
>
>
> You should go ahead and open a jira for this! Please attach the logs to
> that jira. Mark it for 3.3.0 until we can say that it isnt a problem a
Hi ZooKeepers!
The current ZooKeeper client holds strong references to Watcher objects. I
want to change the client so it only holds weak references. Feedback please.
*** Problem Example (contrived, but illustrates point!) ***
I have an application with some large number of virtual "lobbies", eac
Hi Patrick,
thanks for your detailed answer.
>> I'm not sure, but maybe my input could help, too. As I mentioned
>> earlier, I also run the three zookeeper servers not in a local
>> environment but across two sites in different countries (soon, in
>> production, it'll be three sites).
>> I'm acc
12 matches
Mail list logo