[SERVER-78181] Incorrect metric when bucket reopening fails due to duplicate key error Created: 16/Jun/23 Updated: 29/Oct/23 Resolved: 14/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Fausto Leyva (Inactive) | Assignee: | Damian Wasilewicz |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution NAMER
|
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Execution NAMR Team 2023-09-04, Execution NAMR Team 2023-09-18 |
| Participants: |
| Description |
|
"numBucketsOpenedDueToMetadata" will be incremented even when bucket reopening ultimately fails due to duplicate key error. |
| Comments |
| Comment by Githook User [ 13/Sep/23 ] |
|
Author: {'name': 'Damian Wasilewicz', 'email': 'damian.wasilewicz@mongodb.com', 'username': 'DamianWasilewicz'}Message: |