You can't simply leave an element in the queue until a consumer
finishes processing it, otherwise multiple consumers may end up
processing it. What about the following:
- Use a failure detector to detect which consumers are up;
- Before removing an element from the queue, a consumer creates
just to clarify: you also get ConnectionLossException from syncronous requests
if the request cannot be sent or no response is received.
ben
-Original Message-
From: Patrick Hunt [mailto:ph...@apache.org]
Sent: Wednesday, January 07, 2009 10:16 AM
To: zookeeper-user@hadoop.apache.org
The next Bay Area Hadoop User Group meeting is scheduled for Wednesday,
January 21st at Yahoo! 2821 Mission College Blvd, Santa Clara, Building
1, Training Rooms 3 4 from 6:00-7:30 pm.
Agenda:
Hadoop 0.20 Overview - Sameer Paranjpye
Hadoop 1.0 discussion - Sanjay Radia.
Please send me
Live in San Diego/Southern California and want to get together and talk
Hadoop/HBase/Mahout/Zookeeper/Thrift/Cloud/Pig/HBase/etc?
If so, please join us for the first San Diego Hadoop Users Group meeting
that will officially kick-off on January 28, 2009.
The agenda is still TBD, but will
if you do a getData(/a, true) and then /a changes, you will get a watch
event. if /a changes again, you will not get an event. so, if you want to
monitor /a, you need to do a new getData() after each watch event to
reregister the watch and get the new value. (re-registering watches on
It feels like we need a flowchart, state-chart, or something, so we
can all talk about the same thing. Then people could suggest
abstractions that would essentially put a box around sections of the
diagram. However I feel woefully inadequate at the former :(.
.. Adam
On Thu, Jan 8, 2009 at 4:20
