[SERVER-69530] Skip sharding DB check during index builds Created: 08/Sep/22 Updated: 29/Oct/23 Resolved: 20/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc4, 6.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jordi Olivares Provencio | Assignee: | Jordi Olivares Provencio |
| 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 | ||||||||||||||||||||
| Backport Requested: |
v6.1
|
||||||||||||||||||||
| Sprint: | Execution Team 2022-09-19, Execution Team 2022-10-03 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 5 | ||||||||||||||||||||
| Description |
|
In a sharded cluster there is a race condition where dropping a database while building an index can cause a server crash if the abort happens while holding the critical section "lock" for the database. This causes the following invariant to get hit as the error is a StaleDbVersion due to the drop command. Aborting an index while dropping the database should catch the fact we are dropping the database and handle it appropriately by cleaning up. |
| Comments |
| Comment by Githook User [ 28/Sep/22 ] |
|
Author: {'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}Message: |
| Comment by Githook User [ 20/Sep/22 ] |
|
Author: {'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}Message: |