[SERVER-66623] Add network logging to resharding_coordinator_recovers_abort_decision.js test Created: 20/May/22  Updated: 29/Oct/23  Resolved: 23/May/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Marcos José Grillo Ramirez
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
Sprint: Sharding EMEA 2022-05-30
Participants:
Linked BF Score: 6

 Description   

The past logging added to investigate BF-23456 have not been enough to determine the exact cause of the failure. In order to pinpoint the exact node that produced the failure, we need to determine to whom the last _configsvrReshardCollection command was sent from the primary shard.



 Comments   
Comment by Githook User [ 20/May/22 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-66623 Add verbosity on network logging to resharding_coordinator_recovers_abort_decision.js
Branch: master
https://github.com/mongodb/mongo/commit/6f6ea5ea1644e7b6a5bfe8682b4432358e1843b4

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