[jira] Commented: (ZOOKEEPER-202) Phantom ephemeral node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641943#action_12641943 ] Mahadev konar commented on ZOOKEEPER-202: - @flavio yes thats the bug just adding a link here in case someone needs a reference to it... http://sourceforge.net/tracker/index.php?func=detail&aid=1982992&group_id=209147&atid=1008546 > Phantom ephemeral node > -- > > Key: ZOOKEEPER-202 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-202 > Project: Zookeeper > Issue Type: Bug >Reporter: Flavio Paiva Junqueira >Assignee: Flavio Paiva Junqueira > > One of our users has observed that an ephemeral znode had gone away once its > creator had disconnected according to the leader, but one follower believed > that it existed long after the znode had been deleted. Apparently the > follower was never going to delete it. Because the leader wouldn't recognize > the znode as an existing one, any attempt to delete the znode failed. We > have to investigate if this is related to any known bug, although, to my > knowledge, this is the first time it happens. It is important to note that > the user was running an older version of our code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-202) Phantom ephemeral node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641908#action_12641908 ] Benjamin Reed commented on ZOOKEEPER-202: - I think it's 2.1.0 from sourceforge. That release was done on 4/29/2008. (It might have been built earlier.) The latest sourceforge release 2.2.1 has the fix. > Phantom ephemeral node > -- > > Key: ZOOKEEPER-202 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-202 > Project: Zookeeper > Issue Type: Bug >Reporter: Flavio Paiva Junqueira > > One of our users has observed that an ephemeral znode had gone away once its > creator had disconnected according to the leader, but one follower believed > that it existed long after the znode had been deleted. Apparently the > follower was never going to delete it. Because the leader wouldn't recognize > the znode as an existing one, any attempt to delete the znode failed. We > have to investigate if this is related to any known bug, although, to my > knowledge, this is the first time it happens. It is important to note that > the user was running an older version of our code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-202) Phantom ephemeral node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641906#action_12641906 ] Patrick Hunt commented on ZOOKEEPER-202: 1.2.0-130??? That's not a zk version number, any idea which version of zk this corresponds to? (sourceforge has 2.x.x version numbers for example) > Phantom ephemeral node > -- > > Key: ZOOKEEPER-202 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-202 > Project: Zookeeper > Issue Type: Bug >Reporter: Flavio Paiva Junqueira > > One of our users has observed that an ephemeral znode had gone away once its > creator had disconnected according to the leader, but one follower believed > that it existed long after the znode had been deleted. Apparently the > follower was never going to delete it. Because the leader wouldn't recognize > the znode as an existing one, any attempt to delete the znode failed. We > have to investigate if this is related to any known bug, although, to my > knowledge, this is the first time it happens. It is important to note that > the user was running an older version of our code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-202) Phantom ephemeral node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641820#action_12641820 ] Flavio Paiva Junqueira commented on ZOOKEEPER-202: -- Mahadev, Is this the one you're talking about: 1982992 concurrency issue in the zookeeper leader code? > Phantom ephemeral node > -- > > Key: ZOOKEEPER-202 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-202 > Project: Zookeeper > Issue Type: Bug >Reporter: Flavio Paiva Junqueira > > One of our users has observed that an ephemeral znode had gone away once its > creator had disconnected according to the leader, but one follower believed > that it existed long after the znode had been deleted. Apparently the > follower was never going to delete it. Because the leader wouldn't recognize > the znode as an existing one, any attempt to delete the znode failed. We > have to investigate if this is related to any known bug, although, to my > knowledge, this is the first time it happens. It is important to note that > the user was running an older version of our code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-202) Phantom ephemeral node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641788#action_12641788 ] Flavio Paiva Junqueira commented on ZOOKEEPER-202: -- Servers are running 1.2.0-130, built on 04/14/2008. > Phantom ephemeral node > -- > > Key: ZOOKEEPER-202 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-202 > Project: Zookeeper > Issue Type: Bug >Reporter: Flavio Paiva Junqueira > > One of our users has observed that an ephemeral znode had gone away once its > creator had disconnected according to the leader, but one follower believed > that it existed long after the znode had been deleted. Apparently the > follower was never going to delete it. Because the leader wouldn't recognize > the znode as an existing one, any attempt to delete the znode failed. We > have to investigate if this is related to any known bug, although, to my > knowledge, this is the first time it happens. It is important to note that > the user was running an older version of our code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-202) Phantom ephemeral node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641658#action_12641658 ] Patrick Hunt commented on ZOOKEEPER-202: What version of zk is the client/server running? > Phantom ephemeral node > -- > > Key: ZOOKEEPER-202 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-202 > Project: Zookeeper > Issue Type: Bug >Reporter: Flavio Paiva Junqueira > > One of our users has observed that an ephemeral znode had gone away once its > creator had disconnected according to the leader, but one follower believed > that it existed long after the znode had been deleted. Apparently the > follower was never going to delete it. Because the leader wouldn't recognize > the znode as an existing one, any attempt to delete the znode failed. We > have to investigate if this is related to any known bug, although, to my > knowledge, this is the first time it happens. It is important to note that > the user was running an older version of our code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-202) Phantom ephemeral node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641621#action_12641621 ] Flavio Paiva Junqueira commented on ZOOKEEPER-202: -- Unfortunately, the leader logs were not available. We could perhaps take a look at the bugs fixed on sourceforge then, to see if there is one that maps to this problem. > Phantom ephemeral node > -- > > Key: ZOOKEEPER-202 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-202 > Project: Zookeeper > Issue Type: Bug >Reporter: Flavio Paiva Junqueira > > One of our users has observed that an ephemeral znode had gone away once its > creator had disconnected according to the leader, but one follower believed > that it existed long after the znode had been deleted. Apparently the > follower was never going to delete it. Because the leader wouldn't recognize > the znode as an existing one, any attempt to delete the znode failed. We > have to investigate if this is related to any known bug, although, to my > knowledge, this is the first time it happens. It is important to note that > the user was running an older version of our code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-202) Phantom ephemeral node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641615#action_12641615 ] Mahadev konar commented on ZOOKEEPER-202: - i had seen this problem with one of our users earlier and the problem had boiled down to some ptoblem at the leader wherein it got some error while processing the disconnect and didnt send out the disconnect to all the followers.. I think I had fixed it on Source forge. If possible you should take a look at the leaders log to see if you can find something,. > Phantom ephemeral node > -- > > Key: ZOOKEEPER-202 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-202 > Project: Zookeeper > Issue Type: Bug >Reporter: Flavio Paiva Junqueira > > One of our users has observed that an ephemeral znode had gone away once its > creator had disconnected according to the leader, but one follower believed > that it existed long after the znode had been deleted. Apparently the > follower was never going to delete it. Because the leader wouldn't recognize > the znode as an existing one, any attempt to delete the znode failed. We > have to investigate if this is related to any known bug, although, to my > knowledge, this is the first time it happens. It is important to note that > the user was running an older version of our code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
