[
https://issues.apache.org/jira/browse/CASSANDRA-10731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013795#comment-15013795
]
Mike Adamson commented on CASSANDRA-10731:
------------------------------------------
If we are saying that a migration request failing or overrunning is an
indication of the schema not being in sync then we should keep the failure
mechanism. Maybe the test is not strictly correct in that case and is shutting
node1 down at the wrong point. I'll have a play with it and see if that is the
case.
> 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.x
>
>
> 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)
