Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
None
Description
In case or reads, we always get an answer back from db and if it's an error saying "not master", we do a force check master.
But for writes, with default setting, client never gets an answer back and the error goes unnoticed.
A clean fix would be to have updater thread do a forced checkmaster.
This way the max we lose is 5s worth of docs.. which is ok for w=0.
Attachments
Issue Links
- is related to
-
SERVER-1679 need to be a way to quickly detect a loss of primary state in a replica set if one is not calling getlasterror
-
- Closed
-