If a write hits the wrong shard, immediately after a migrate, and has to go through the writebackListener then the getLastError call returns n:0.
We should indicate a special state (writeback:true, or n:-1, or something) if we can't correctly report the "n" value.
- related to
-
SERVER-5243 mongos will route getLastError command to the config server when last insert triggered a split
- Closed