Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
-
Sharding
-
ALL
Description
In general, it takes a lot of sleuthing to figure out exactly which shard sent back a stale config error and why the shard was stale, in human-readable terms. This causes a disproportionate amount of support load, just figuring out what is actually wrong.
We could change these messages to be much more descriptive:
"shardXXX thinks the collection foo.bar is at a newer version XXX", etc.
Attachments
Issue Links
- related to
-
SERVER-11688 Improve diagnostic messages for metadata reloading in shards
-
- Closed
-