cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Adamson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10731) Bootstrap starts before migration responses have completed
Date Wed, 18 Nov 2015 18:37:10 GMT


Mike Adamson commented on CASSANDRA-10731:

The proposed solution for this is as follows. 

{{MigrationTask}} maintains a queue of {{CountdownLatch}} that complete as each response callback
completes. {{MigrationManager.isReadyForBootstrap}} returns {{true}} if the queue is empty.
If the queue is not empty then a new method {{MigrationManager.waitTillReadyForBootstrap}}
is called by {{StorageService}}. This waits on each latch in the queue until they complete.
The wait uses a system property {{cassandra.migration_task_wait_in_seconds}} defined timeout
which defaults to 1 second.

> Bootstrap starts before migration responses have completed
> ----------------------------------------------------------
>                 Key: CASSANDRA-10731
>                 URL:
>             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

View raw message