[SERVER-45770] Add to information contained in logfile about "moveChunk.to" Created: 24/Jan/20 Updated: 29/Oct/23 Resolved: 25/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.5, 3.6.18, 4.3.4, 4.0.17 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Giuliano Celani | Assignee: | Josef Ahmad |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v4.2, v4.0, v3.6
|
||||
| Participants: | |||||
| Description |
|
Current log files for shards do not have consistency between "moveChunk.from" and moveChunk.to" log events. moveChunk.from provides both source shard and destination shard fields whilst moveChunk.to does not. I am aware that this can be sourced from previous events such as moveChunk.commit, but it will be a lot better if the information can be gathered from one line moveChunk.from:
moveChunk.to:
|
| Comments |
| Comment by Githook User [ 06/Mar/20 ] |
|
Author: {'username': 'josefahmad', 'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com'}Message: (cherry picked from commit 742ac9b37b1d8f489e1b259a0a3575f8811edac4) Conflicts: |
| Comment by Githook User [ 06/Mar/20 ] |
|
Author: {'name': 'Josef Ahmad', 'username': 'josefahmad', 'email': 'josef.ahmad@mongodb.com'}Message: (cherry picked from commit 742ac9b37b1d8f489e1b259a0a3575f8811edac4) Conflicts: |
| Comment by Githook User [ 06/Mar/20 ] |
|
Author: {'name': 'Josef Ahmad', 'username': 'josefahmad', 'email': 'josef.ahmad@mongodb.com'}Message: (cherry picked from commit 742ac9b37b1d8f489e1b259a0a3575f8811edac4) Conflicts: |
| Comment by Githook User [ 25/Feb/20 ] |
|
Author: {'username': 'josefahmad', 'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com'}Message: |