Version
Cb Response 6.x
Issue
While upgrading, a single node is taking significantly longer than the others to finish migrating events
Cause
The process documents on this node are far larger than the other minions so it is taking longer to process these documents.
Solution
This is normal behavior. It is rare, but migration process can take over an hour to complete.
Warning: Do not interrupt the upgrade process prior to this point or it could corrupt the new legacy core. If you have already done so, you can run a disk activity monitor such as iotop or iostats. If there is very little activity that could suggest core corruption:
iotop
If there is very little activity you can open a case with support: Create a Case in The Community
Thank you for your feedback.
Your feedback has been submitted and will be reviewed.