[SERVER-63337] Increase log level in failing test Created: 07/Feb/22  Updated: 29/Oct/23  Resolved: 08/Feb/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.3.0

Type: Task Priority: Minor - P4
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-02-07, Sharding EMEA 2022-02-21
Participants:
Linked BF Score: 6

 Description   

After investigating BF-23456 the following hypothesis has been developed:

There is an interaction between the RSM and the ShardRegistry (most likely due to a HostUnreachable error) that temporarily prevents requests to the shard registry to be successful, making the ARS to return shard not found. However, the exact scenario haven't been determined, so, in order to confirm or refine the hypothesis, we need more information from the logs, and, due to the fact that the problem has not been reproduced locally, the best idea for now is to increase the log level of the resharding_coordinator_recovers_abort_decision.js test and wait for the next failure.



 Comments   
Comment by Githook User [ 08/Feb/22 ]

Author:

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

Message: SERVER-63337 Add option to change log level in resharding tests
Branch: master
https://github.com/mongodb/mongo/commit/3d2f94f2ae5ee75c56adb6d29f35cfc74f81a181

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