-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 18 (08/05/16), Sharding 2016-08-29
-
(copied to CRM)
3.4 onwards:
a shard can become shard aware in two ways:
- started with --shardsvr and shardIdentity document found on disk
- started with --shardsvr and receive shardIdentity insert
so, we will eventually reject all sharding commands if:
- not started with --shardsvr
- started with --shardsvr but not yet sharding aware
=============
for backwards compatibility with 3.2:
a shard can also become shard aware if:
- started with --shardsvr and receive command that initializes sharding awareness
so (what this ticket does):
reject all sharding commands except a whitelist of commands that initialize sharding awareness.
- is related to
-
SERVER-25910 fail setShardVersion on mongod if not running with --shardsvr
- Closed
-
SERVER-23764 Reject most operations when a mongod is started with --shardsvr but hasn't yet been added as a shard
- Closed
- related to
-
SERVER-24352 configs initialize sharding awareness on sharding-unaware shards on transition to primary
- Closed
-
SERVER-25417 harden checks around using --shardSvr, --overrideShardIdentity, and queryableBackupMode
- Closed
-
SERVER-25543 add "shardsvr" startup option for shards in ShardedClusterFixture
- Closed
-
SERVER-25549 re-enable read_only_sharded suite
- Closed