[ https://issues.apache.org/jira/browse/QPID-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249832#comment-13249832 ]
Jason Dillaman commented on QPID-3369: -------------------------------------- I believe the issue would still exist, but we didn't run into a case where the cluster elder crashed during our latest round of testing. > Loss of cluster elder can result in loss of whole cluster > --------------------------------------------------------- > > Key: QPID-3369 > URL: https://issues.apache.org/jira/browse/QPID-3369 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering > Affects Versions: 0.7 > Reporter: Jason Dillaman > Assignee: Alan Conway > Fix For: Future > > Attachments: QPID-3369.patch > > > If the cluster elder is lost, it is possible that the remaining nodes of the > cluster will fail with the following errors: > Error delivering frames: Cluster timer wakeup non-existent task > ManagementAgent::periodicProcessing (qpid/cluster/ClusterTimer.cpp:93) > -- or -- > Error delivering frames: Cluster timer drop non-existent task > ManagementAgent::periodicProcessing (qpid/cluster/ClusterTimer.cpp:109) > When a member is promoted to be the elder, the ClusterTimer::becomeElder() > method will add all the current cluster tasks to the Timer. However, there is > a potential race condition where CPG can deliver the timer wakeup from the > original elder. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org