[SERVER-53187] Structured log improvements to split_vector/chunk_splitter lines 22107 and 21908 Created: 02/Dec/20 Updated: 29/Oct/23 Resolved: 03/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.4.2 |
| Fix Version/s: | 4.4.7, 5.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Sedor | Assignee: | Paolo Polato |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
Log line 22107 ("Requested split points lookup") logs dehydrated minKey and maxKey attributes as structured data, which for compound shard keys could present the same parsing difficulties for duplicate key names discussed in An operationally related log line, 21908 ("autpsplitted chunk") does have a readable, hydrated chunk range, but it's within a single semi-structured chunk string that includes shard, lastmod, and a hydrated chunk key range (this seems to be from chunk.toString(). I think that ideally we would have the best of both worlds in each of these lines, structured data AND a hydrated key range. To provide a specific request as a strawperson: 1) In 22107, hydrate minKey and maxKey values |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 08/Jun/21 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: (cherry picked from commit 02f0f34d9ab3d1449bad869aabdd478a5de0791d) |
| Comment by Githook User [ 03/Jun/21 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: |