When a new collection is added and its data is migrated to another shard (from the primary shard), any mongos which had already authenticated a user to that DB before the collection is sharded and data move happened now cannot see this collection's data on the other shard.
I think this may be related to mongod setting shard version for that collection to 0 when last chunk is migrated off of it, but that's problematic possibly in similar way we require flushRouterConfig when movePrimary is done for a database.
- duplicates
-
SERVER-10758 Strict Epoch comparison
- Closed
- is duplicated by
-
SERVER-13531 Collection drop doesn't clean the shard version on empty shards
- Closed
- related to
-
SERVER-7783 Audit code which finds system.users database for authentication in mongos
- Closed
-
SERVER-16316 Remove unsupported behavior in shard3.js
- Closed
-
SERVER-939 Ability to distribute collections in a single db
- Closed