[SERVER-47720] Clarify "RecordId(...) not found in the index for key" log message Created: 23/Apr/20 Updated: 29/Oct/23 Resolved: 16/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0, 4.0.25, 4.2.15, 4.4.7 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Eric Sedor | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.4, v4.2, v4.0
|
||||||||
| Sprint: | Execution Team 2020-06-29 | ||||||||
| Participants: | |||||||||
| Description |
|
This log line can appear without much other context, and seems to be benign in some (most?) cases. While it seems possible to infer what is going on, logging the index name and collection namespace would speed up diagnosis by referencing the exact index to reason about. |
| Comments |
| Comment by Githook User [ 17/May/21 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: (cherry picked from commit 6ea7d1923619b600ea0f16d7ea6e82369f288fd4) |
| Comment by Githook User [ 17/May/21 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: (cherry picked from commit 6ea7d1923619b600ea0f16d7ea6e82369f288fd4) |
| Comment by Githook User [ 17/May/21 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: (cherry picked from commit 6ea7d1923619b600ea0f16d7ea6e82369f288fd4) |
| Comment by Githook User [ 16/Jun/20 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |