[SERVER-57356] Better logging around failed chunk migration Created: 02/Jun/21  Updated: 29/Oct/23  Resolved: 02/Jun/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.0.24
Fix Version/s: 4.0.25

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

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Participants:
Linked BF Score: 0

 Description   

This is to address the fresh flakiness in the 4.0 branch of the change_stream_shard_failover.js test, which fails the chunk migration during failover. The failure logged at client side:
"moveChunk command failed on source shard. :: caused by :: NotMaster: not master"
I think logging this at replica side to detect where and when the migration command failed would help.

The flakiness is very recent (since May 28) and we should understand if recent changes triggered it. I cannot reproduce it locally, never fails.



 Comments   
Comment by Githook User [ 02/Jun/21 ]

Author:

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

Message: SERVER-57356: Better logging around failed chunk migration
Branch: v4.0
https://github.com/mongodb/mongo/commit/ec0158de27c891599c2d442c0e8c92275b7d23b8

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