[SERVER-38470] Add more logging to TransactionRouter Created: 07/Dec/18 Updated: 29/Oct/23 Resolved: 16/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2018-12-17 | ||||
| Participants: | |||||
| Linked BF Score: | 14 | ||||
| Description |
|
More logging in the TransactionRouter (at a high verbosity level) would make diagnosing failures easier, particularly while sharded transactions are being stabilized. A few things that could be logged:
|
| Comments |
| Comment by Githook User [ 16/Dec/18 ] |
|
Author: {'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow'}Message: |