curator-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jordan Zimmerman <jor...@jordanzimmerman.com>
Subject Re: protection on ephemeral nodes can go haywire
Date Wed, 15 Jan 2014 00:52:47 GMT
OK - please add an issue on Curator’s Jira and a test case.

-JZ

From: Erik Nelson Erik Nelson
Reply: Erik Nelson erik@gravity.com
Date: January 14, 2014 at 4:52:21 PM
To: Jordan Zimmerman jordan@jordanzimmerman.com
Subject:  Re: protection on ephemeral nodes can go haywire  
This is curator 2.3 and zookeeper 3.4.5-cdh4.3.2

On Jan 14, 2014, at 4:44 PM, Jordan Zimmerman <jordan@jordanzimmerman.com> wrote:

That looks like a bug to me. The GUID should only be present once. I remember there being
a bug like this a long time ago. What version are you using?

-JZ

From: Erik Nelson Erik Nelson
Reply: user@curator.apache.org user@curator.apache.org
Date: January 14, 2014 at 4:43:02 PM
To: user@curator.apache.org user@curator.apache.org
Subject:  protection on ephemeral nodes can go haywire 
I've noticed that it is quite common for my list of nodes to contain a bunch of entries that
look like: 

/_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-_c_35528b0e-9e81-4bc2-8f3d-4e64198dc5cc-[actual
node name] 

sometimes even with the protection guid repeated again with the same actual node name. 

This can get to the point where I start get exceptions on the client where it complains about
the node name needing to begin with '/'; I believe that the name exceeds the maximum size
and is being truncated. 

Is this a known issue? My use of persistentephemeralnode isn't too fancy, and this happens
without any badness in the quorum. I've looked through the jira issues but can't find anything
related. 

Thanks, 

erik


Mime
View raw message