[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: |
|
||||
| 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: 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: |