-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.0.6, 2.2.0-rc0
-
Component/s: Replication, Sharding
-
ALL
We were performing a series of restarts of config servers and shards. While some of the servers were rebooting, mongos that used them occasionally returned the following error:
{ "ok" : 0.0, "errmsg" : "" }).
Our auto-retry framework relies on a set of error codes and/or messages and can't cope with such errors. Emitting a more descriptive error and assigning this kind of error an error code (even generic one) would be very helpful both for diagnosing reasons of the error and attempting to recover from it.
- duplicates
-
SERVER-6581 mongos GLE needs to report errmsg when sub-GLE commands error on shard/shards
- Closed
- related to
-
SERVER-8984 DBClientInterface::getLastError should test for command failures
- Closed