Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
ALL
-
v6.0
-
fcbis-sharding-bug.patch
./buildscripts/resmoke.py run --storageEngine=wiredTiger --storageEngineCacheSizeGB=.50 --suite=sharding jstests/sharding/fcbis-sharding.js --log=file
Need to have built with enterprise support for FCBIS. -
Sharding EMEA 2022-04-18, Sharding EMEA 2022-05-02, Sharding EMEA 2022-05-16
-
124
Description
initializeGlobalShardingStateForMongoD has to be run on shardsvrs during initialization. Currently, this is triggered from the following places:
1) In initAndListen
2) In ShardServerOpObserver::onInserts when an insert of the shard identity document is observed.
For FCBIS however, this does not work: On a new member that will undergo initial sync, point (1) will not find the shard identity document at all. Later, point (2) will not be triggered because FCBIS does not perform inserts like logical initial sync would.
As a result, after FCBIS has completed, the shard is left with uninitialized sharding state.
Attachments
Issue Links
- depends on
-
SERVER-65251 FCBIS doesn't call to the onInitialSyncComplete ReplicaSetAwareService hook
-
- Closed
-
-
SERVER-64627 Need general method to handle in-memory state after initial sync
-
- Closed
-
- is depended on by
-
-
- Closed
-
- is related to
-
-
- Backlog
-
- related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-