[ 
https://issues.apache.org/jira/browse/CASSANDRA-19208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809462#comment-17809462
 ] 

Alex Petrov commented on CASSANDRA-19208:
-----------------------------------------

Committed to trunk with [b10e2693443bb5eb5c9b3d561f8d5e47ac092a8c 
|https://github.com/apache/cassandra/commit/b10e2693443bb5eb5c9b3d561f8d5e47ac092a8c]

> Fix ClusterMetadataUpgradeHarryTest
> -----------------------------------
>
>                 Key: CASSANDRA-19208
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19208
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Alex Petrov
>            Assignee: Alex Petrov
>            Priority: Normal
>             Fix For: 5.1
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Unfortunately I do not have a stack trace handy, but the test was essentially 
> timing out after CMS was falling into an infinite loop during initialisation. 
> A problem was caused by the fact that if there is a paxos timeout during 
> propose phase, CMS would get stuck in an infinite loop trying to catch up, 
> and not finding anything to catch up from.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to