[SERVER-41799] Update shard_aware_init to flush its shard identity before shutdown Created: 17/Jun/19 Updated: 29/Oct/23 Resolved: 19/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.0-rc3, 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Mira Carey |
| 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: |
v4.2
|
||||||||||||||||
| Sprint: | Service Arch 2019-07-01 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 16 | ||||||||||||||||
| Description |
|
We currently spin up sharding in advance of replication (see It's going to be quite difficult to untangle all the dependencies between sharding and replication, and in the mean while shard_aware_init has more failures than we'd like. See BF-12759. That particular test specifically checks that corrupting our version (via a manual update to admin.system.version) causes mongod to crash on startup. The problem is that because we start sharding before replication (and also do a complicated dance of restarting in standalone mode to corrupt the document), we can perform an update when the document we want to modify isn't present (because it's still in the oplog and we're in standalone mode), and then fail to crash on startup. So let's fix up that test by waiting to flush the oplog before shutting down the node (when in replica set mode). |
| Comments |
| Comment by Githook User [ 26/Jun/19 ] |
|
Author: {'name': 'Jason Carey', 'email': 'jcarey@argv.me', 'username': 'hanumantmk'}Message: We currently spin up sharding in advance of replication (see It's going to be quite difficult to untangle all the dependencies So let's fix up that test by waiting to flush the oplog before shutting (cherry picked from commit 303adb5e50eb02d077b734aa27ae8d02a781d7a2) |
| Comment by Githook User [ 19/Jun/19 ] |
|
Author: {'name': 'Jason Carey', 'email': 'jcarey@argv.me', 'username': 'hanumantmk'}Message: We currently spin up sharding in advance of replication (see It's going to be quite difficult to untangle all the dependencies So let's fix up that test by waiting to flush the oplog before shutting |