[SERVER-65065] Improve logging when configsvr coordinator fails Created: 30/Mar/22 Updated: 29/Oct/23 Resolved: 25/Apr/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 | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-05-02 |
| Participants: |
| Description |
|
After executing a coordinator instance, the ConfigsvrCoordinator is doing a conditional print. We should print the error unconditionally and add a comment explaining why we don't cancel the completion promise. |
| Comments |
| Comment by Githook User [ 25/Apr/22 ] |
|
Author: {'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: |
| Comment by Marcos José Grillo Ramirez [ 22/Apr/22 ] |
|
After doing an analysis of the code, there is actually no bug, so, this ticket is being repurposed to improve logging in case of error in the configsvr coordinator. |