You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2011/04/26 21:37:03 UTC
[jira] [Created] (CASSANDRA-2565) Nodes are not reported as alive
after being marked down
Nodes are not reported as alive after being marked down
-------------------------------------------------------
Key: CASSANDRA-2565
URL: https://issues.apache.org/jira/browse/CASSANDRA-2565
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 0.8 beta 1
Reporter: Brandon Williams
Fix For: 0.8.0
To reproduce: start two nodes in foreground mode, then suspend (^Z) one of them. Once it is marked down, resume the process (fg) and it will not be marked up again.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CASSANDRA-2565) Nodes are not reported as alive
after being marked down
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams reassigned CASSANDRA-2565:
-------------------------------------------
Assignee: Brandon Williams
> Nodes are not reported as alive after being marked down
> -------------------------------------------------------
>
> Key: CASSANDRA-2565
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2565
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8 beta 1
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Fix For: 0.8.0
>
> Attachments: 2565.txt
>
>
> To reproduce: start two nodes in foreground mode, then suspend (^Z) one of them. Once it is marked down, resume the process (fg) and it will not be marked up again.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CASSANDRA-2565) Nodes are not
reported as alive after being marked down
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025394#comment-13025394 ]
Brandon Williams edited comment on CASSANDRA-2565 at 4/26/11 7:41 PM:
----------------------------------------------------------------------
Looks like in the Big Gossip Refactor there was a slight regression. We avoid notifying if there's not a major state change, however we also need to see if the node was previously dead and if so, notify.
was (Author: brandon.williams):
Looks like in the Big Gossip Refactor there was a slightly regression. We avoid notifying if there's not a major state change, however we also need to see if the node was previously dead and if so, notify.
> Nodes are not reported as alive after being marked down
> -------------------------------------------------------
>
> Key: CASSANDRA-2565
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2565
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8 beta 1
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Fix For: 0.8.0
>
> Attachments: 2565.txt
>
>
> To reproduce: start two nodes in foreground mode, then suspend (^Z) one of them. Once it is marked down, resume the process (fg) and it will not be marked up again.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2565) Nodes are not reported as alive
after being marked down
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-2565:
----------------------------------------
Attachment: 2565.txt
> Nodes are not reported as alive after being marked down
> -------------------------------------------------------
>
> Key: CASSANDRA-2565
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2565
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8 beta 1
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Fix For: 0.8.0
>
> Attachments: 2565.txt
>
>
> To reproduce: start two nodes in foreground mode, then suspend (^Z) one of them. Once it is marked down, resume the process (fg) and it will not be marked up again.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2565) Nodes are not reported as alive
after being marked down
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025501#comment-13025501 ]
Hudson commented on CASSANDRA-2565:
-----------------------------------
Integrated in Cassandra-0.8 #43 (See [https://builds.apache.org/hudson/job/Cassandra-0.8/43/])
Mark nodes that were previously down as alive, even without a major
state change.
Patch by brandonwilliams, reviewed by jbellis for CASSANDRA-2565
> Nodes are not reported as alive after being marked down
> -------------------------------------------------------
>
> Key: CASSANDRA-2565
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2565
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8 beta 1
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Fix For: 0.8.0
>
> Attachments: 2565.txt
>
>
> To reproduce: start two nodes in foreground mode, then suspend (^Z) one of them. Once it is marked down, resume the process (fg) and it will not be marked up again.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2565) Nodes are not reported as alive
after being marked down
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025450#comment-13025450 ]
Jonathan Ellis commented on CASSANDRA-2565:
-------------------------------------------
+1
> Nodes are not reported as alive after being marked down
> -------------------------------------------------------
>
> Key: CASSANDRA-2565
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2565
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8 beta 1
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Fix For: 0.8.0
>
> Attachments: 2565.txt
>
>
> To reproduce: start two nodes in foreground mode, then suspend (^Z) one of them. Once it is marked down, resume the process (fg) and it will not be marked up again.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CASSANDRA-2565) Nodes are not reported as alive
after being marked down
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams resolved CASSANDRA-2565.
-----------------------------------------
Resolution: Fixed
Committed.
> Nodes are not reported as alive after being marked down
> -------------------------------------------------------
>
> Key: CASSANDRA-2565
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2565
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8 beta 1
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Fix For: 0.8.0
>
> Attachments: 2565.txt
>
>
> To reproduce: start two nodes in foreground mode, then suspend (^Z) one of them. Once it is marked down, resume the process (fg) and it will not be marked up again.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2565) Nodes are not reported as alive
after being marked down
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-2565:
----------------------------------------
Attachment: (was: 2565.txt)
> Nodes are not reported as alive after being marked down
> -------------------------------------------------------
>
> Key: CASSANDRA-2565
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2565
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8 beta 1
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Fix For: 0.8.0
>
> Attachments: 2565.txt
>
>
> To reproduce: start two nodes in foreground mode, then suspend (^Z) one of them. Once it is marked down, resume the process (fg) and it will not be marked up again.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2565) Nodes are not reported as alive
after being marked down
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-2565:
----------------------------------------
Attachment: 2565.txt
Looks like in the Big Gossip Refactor there was a slightly regression. We avoid notifying if there's not a major state change, however we also need to see if the node was previously dead and if so, notify.
> Nodes are not reported as alive after being marked down
> -------------------------------------------------------
>
> Key: CASSANDRA-2565
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2565
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8 beta 1
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Fix For: 0.8.0
>
> Attachments: 2565.txt
>
>
> To reproduce: start two nodes in foreground mode, then suspend (^Z) one of them. Once it is marked down, resume the process (fg) and it will not be marked up again.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira