[SERVER-30611] Failure to commit chunk migration due to config server shut down fasserts Created: 11/Aug/17 Updated: 27/Oct/23 Resolved: 30/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
This is the current shutdown check in the migration critical section: https://github.com/mongodb/mongo/blob/77076b4121dbf89c1c7789e4c3b06e591e594d0d/src/mongo/db/s/migration_source_manager.cpp#L358-L365. However, it only successfully obviates fassert if globalInShutdownDeprecated() is true on the shard. So if the config server is shutting down and returns the error, the shard will fassert. |
| Comments |
| Comment by Kaloian Manassiev [ 30/Sep/20 ] |
|
As of the changes done for |