[SERVER-51228] dbHash should return SnapshotUnavailable if _id index is not visible in the current snapshot Created: 29/Sep/20 Updated: 29/Oct/23 Resolved: 05/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Louis Williams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Execution Team 2020-10-05, Execution Team 2020-10-19 | ||||
| Participants: | |||||
| Linked BF Score: | 21 | ||||
| Description |
|
The test-only command 'emptycapped' drops and recreates all indexes. Because of this, it is possible for dbHash to pick a read timestamp where the new _id index is not visible yet. Instead of returning a 'no _id index' error, dbHash should return a SnapshotUnavailable error, which is already an expected and routine error code. This problem can be fixed by having 'emptycapped' set the collection's minimumVisibleSnapshot. |
| Comments |
| Comment by Githook User [ 03/Oct/20 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: |
| Comment by Githook User [ 02/Oct/20 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: Revert " This reverts commit 00cc67fc18f2ef81a2d08d962eca1f2907e3b51e. |
| Comment by Githook User [ 01/Oct/20 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: |