[SERVER-31739] on failed insert keysInserted should reset back to 0 Created: 26/Oct/17 Updated: 07/Feb/22 Resolved: 07/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | 4.4.6, 5.0.0-rc3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | Romans Kasperovics |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | query-44-grooming | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | QE 2022-02-07, QE 2022-02-21, QE 2022-01-24 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
In case insert fails I see this in the logs:
That keysInserted:1 is incorrect. |
| Comments |
| Comment by Romans Kasperovics [ 07/Feb/22 ] |
|
The fix for |
| Comment by Romans Kasperovics [ 04/Feb/22 ] |
|
This ticket will be resolved by the pull-request https://github.com/10gen/mongo/pull/2753 also resolving |
| Comment by Kyle Suarez [ 29/Jun/21 ] |
|
mindaugas.malinauskas has worked on a fix for this previously, but the fix was harder than expected due to some trickiness with the update path. Scheduling this for a future sprint for someone to investigate a comprehensive solution that does not involve adding custom rollback code to multiple parts of the code (e.g. using RecoveryUnit::Change?) |
| Comment by Kyle Suarez [ 23/Jun/21 ] |
|
I'm not sure which branches this bug affects, but since it seems to have occurred at least on 4.4.1, I'm adding "Affects Versions" for the latest 4.4.x and 5.0.x branches. |