Hi all,
I have a question about the way setACL functions. It seems that the
PreRequestProcessor handles all kinds of requests the same, checks the
validity of the corresponding ACL, and enqueues them to Sync and Final
processors. Maybe I am missing something here, but this behaviour seems
More or less, yes.
If the requests are from the same client, then you say that there will
not be a problem? I guess that is true if you always wait for the
response of the first request in order to execute the second. I am not
sure if that is a requirement for all Zookeeper client
Mahadev, is it true that a lagging follower, participating in the
ensemble but not part of the quorum, would continue to respond to read
requests until it had received/processed the update from the leader?
Patrick
Mahadev Konar wrote:
HI Manos,
The accepting of a txn for being processed
Yes that is true.
mahadev
On 2/10/09 4:54 PM, Patrick Hunt ph...@apache.org wrote:
Mahadev, is it true that a lagging follower, participating in the
ensemble but not part of the quorum, would continue to respond to read
requests until it had received/processed the update from the leader?
To: zookeeper-dev@hadoop.apache.org
Subject: Re: setACL semantics
More or less, yes.
If the requests are from the same client, then you say that there will
not be a problem? I guess that is true if you always wait for the
response of the first request in order to execute the second. I am not
sure
: Tuesday, February 10, 2009 4:34 PM
To: zookeeper-dev@hadoop.apache.org
Subject: Re: setACL semantics
More or less, yes.
If the requests are from the same client, then you say that there will
not be a problem? I guess that is true if you always wait for the
response of the first request in order
