-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
Sharding NYC 2022-04-18
-
2
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Exact error "Config shard selected, while operation is not on admin or config DB". It's massively present in my run and should be high priority.
Tests to reproduce (just random few):
jstests/sharding/accurate_count_with_predicate.js jstests/sharding/addshard5.js jstests/sharding/aggregations_in_session.js jstests/sharding/allow_partial_results.js jstests/sharding/allow_partial_results_nshards.js jstests/sharding/api_params_nontransaction_sharded.js jstests/sharding/api_params_transaction_sharded.js jstests/sharding/api_version_test_expression.js jstests/sharding/array_shard_key.js jstests/sharding/authConnectionHook.js jstests/sharding/auth_add_shard.js jstests/sharding/balancer_collection_status.js jstests/sharding/balancer_defragmentation_merge_chunks.js jstests/sharding/basic_merge.js jstests/sharding/basic_split.js ...
about half of all failures.
- depends on
-
SERVER-65407 In ShardingCatalogManager::commitChunkMigration() operations on config DB should pass config arg
-
- Closed
-