[SERVER-70263] Incorrect name for pauseBeforeInsertCoordinatorDoc failpoint Created: 05/Oct/22 Updated: 29/Oct/23 Resolved: 14/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Abdul Qadeer | Assignee: | Jada Lilleboe (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, sharding-nyc-subteam1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding NYC
|
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Participants: | |
| Story Points: | 1 |
| Description |
|
The failpoint is activated in the code after the resharding coordinator doc is inserted into DB. However the name implies that it is done before; which can cause confusion and errors. It needs to be renamed as pauseAfterInsertCoordinatorDoc. |
| Comments |
| Comment by Githook User [ 14/Jun/23 ] |
|
Author: {'name': 'Jada Lilleboe', 'email': 'jada.lilleboe@mongodb.com', 'username': 'jadalilleboe'}Message: |
| Comment by Max Hirschhorn [ 24/Oct/22 ] |
|
Looking at the existing usages we're ok to rename pauseBeforeInsertCoordinatorDoc to pauseAfterInsertCoordinatorDoc to reflect its actual usage. However, to avoid a failure in the implicit multiversion testing with mixed binary version clusters we should change the failpoint used in resharding_disallow_drop.js to another one which will prevent the resharding operation from completing such as reshardingPauseCoordinatorBeforeInitializing. |