servers in standalone
mode and then merging. can you explain that a bit more?
thanx
ben
On 11/01/2010 04:51 PM, Jeremy Stribling wrote:
I think this is caused by stupid behavior on our application's part, and
the error message just confused me. Here's what I think is happening.
1) 3 servers are up
Thanks for the reply. It happened every time we called create, not just
once. More than that, we tried restarting each of the nodes in the
system (one-by-one), including the new master, and the problem continued.
Unfortunately we cleaned everything up, and it's not in that state
anymore.
,
though I have sequence numbers on that record prefix up to 214 or so.
There seem to be some gaps though -- I thin ls /zkrsm only shows about
177. Not sure if that's relevant or not.
Thanks,
Jeremy
On 11/01/2010 12:06 PM, Jeremy Stribling wrote:
Thanks for the reply. It happened every time we
.
(If this explanation sounds totally off-base though, let me know. I'm
not 100% certain this is what's happening, but it definitely seems likely.)
Thanks,
Jeremy
On 11/01/2010 02:56 PM, Jeremy Stribling wrote:
Yes, every znode in /zkrsm was created with the sequence flag.
We bring up a cluster
HI everyone,
Is there any situation in which creating a new ZK node with the SEQUENCE
flag should result in a node exists error? I'm seeing this happening
after a failure of a ZK node that appeared to have been the master; when
the new master takes over, my app is unable to create a new
Can the server id in the myid field be any valid long value? I'm
interested in generating, rather than pre-assigning, a unique id for
every server, so my current plan is to convert the server's IP address
into a 32-bit integer, and use the decimal, ASCII representation of that
integer for the
