-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.6.16, 4.2.2, 4.0.14
-
Component/s: Sharding
-
Sharding
-
ALL
The only sharded collection which has the config server as the primary shard is config.system.sessions. Unfortunately, the code path that the config server calls to create indexes on the sessions collection would currently invariant if one of the targeted shards was the config server itself. To get around this, index commands do not target the config shard, but as a result, listIndexes on config.system.sessions will not return the correct indexes. This bug existed prior to 4.4 as well, since the old code to create indexes on the sessions collection also did not build the index on the config server.
- is related to
-
SERVER-45102 Sharded listIndexes should always target a shard that owns chunks
- Closed