You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Chris Love (JIRA)" <ji...@apache.org> on 2016/06/12 04:59:21 UTC

[jira] [Commented] (CASSANDRA-10731) Bootstrap starts before migration responses have completed

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

Chris Love commented on CASSANDRA-10731:
----------------------------------------

This may be causing me some issues.  I am backing out these changes from 3.6 and testing.  See https://issues.apache.org/jira/browse/CASSANDRA-11983

> Bootstrap starts before migration responses have completed
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-10731
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10731
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Streaming and Messaging
>            Reporter: Mike Adamson
>            Assignee: Mike Adamson
>             Fix For: 3.0.1, 3.1
>
>
> We have a number of failing tests running on slow VMs that are failing because {{MigrationManager.isReadyForBootstrap}} is return {{true}} when there are still inflight responses being processed to migration requests. This is happening because the {{MigrationTask.runMayThrow}} has completed but the {{IAsyncCallback.response}} is still running.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)