[SERVER-59881] Add logging to tenant_migration_concurrent_migrations_stress_test.js to find possible discrepancy in currentOp report Created: 10/Sep/21  Updated: 29/Oct/23  Resolved: 10/Sep/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 5.1 Required
Fix Version/s: 5.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Andrew Shuvalov (Inactive) Assignee: Andrew Shuvalov (Inactive)
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Participants:
Linked BF Score: 141

 Description   

The test tenant_migration_concurrent_migrations_stress_test is using 
currentOp command to wait for all migrations to complete. In every stuck test one or more migrations is in Aborted state fetched from the currentOp output, however from the actual log all migrations completed without error.
 
The currentOp takes `_durableState.state` value to report on migration state. This investigation may prove that the `_durableState.state` might be in Aborted state for a migration that completed without error.
 
This bug is to improve diagnostics.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 10/Sep/21 ]

Author:

{'name': 'Andrew Shuvalov', 'email': 'andrew.shuvalov@mongodb.com', 'username': 'shuvalov-mdb'}

Message: SERVER-59881 log an aborted migration in test
Branch: master
https://github.com/mongodb/mongo/commit/a144ad58c9781602e99941fe627eceed8e7bc8bb

Generated at Thu Feb 08 05:48:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.