-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2020-04-20
-
21
PM-1361 changed the protocol for index modifying commands on sharded collections to require shard versions and for the execution of these commands to be mutually exclusive with the migration critical section. To verify this, a dassert was added that there is not an active critical section when the corresponding opObserver method for each index command is run. This dassert is not valid for index commands run directly against a shard, because they will not contain a shard version. Some of our testing hooks, like checkReplDBHash, use a ReplSetTest method that runs noop collMods on every non-system collection to wait for background index activity to complete, which can trigger the dassert.
Restricting the dassert to only apply to commands sent on an internal connection (i.e. from a mongod or mongos) should avoid these failures while allowing it to serve its intended purpose.
- is related to
-
SERVER-45017 [correct indexes] Remove index commands upgrade/downgrade code when 4.4 becomes last stable
- Closed
- related to
-
SERVER-48089 Blacklist move_chunk_critical_section_non_internal_client_abort.js from mixed version suites
- Closed