MigrationManager.java:164 - Migration task failed to complete

["Zhang, Charles" <Co...@fmr.com>]

I have seen a bunch of them in the log files of some newly joined nodes. I did a search in google and it seems increasing the countdown latch timeout can solve this problem. But I assume it only resolves it for future nodes when joining happens? For the existing nodes, anything needs to be done?

Re: MigrationManager.java:164 - Migration task failed to complete

[Alain RODRIGUEZ <ar...@gmail.com>]

There is not that much context here, so I will do a standard answer too.

If you have a doubt regarding the data owned by a node, running repair
takes some resources but should never break anything. I mean it is an
operation you can be running as much as you want. So I would use it, just
in case.

If the repair finishes successfully, your data is now consistent.

C*heers,
-----------------------
Alain Rodriguez - alain@thelastpickle.com
France

The Last Pickle - Apache Cassandra Consulting
http://www.thelastpickle.com

2016-05-03 20:09 GMT+02:00 Zhang, Charles <Co...@fmr.com>:

> I have seen a bunch of them in the log files of some newly joined nodes. I
> did a search in google and it seems increasing the countdown latch timeout
> can solve this problem. But I assume it only resolves it for future nodes
> when joining happens? For the existing nodes, anything needs to be done?
>