-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication, Sharding, Write Ops
-
None
-
Sharding
Much like getLastError (SERVER-4073) the write commands should return back information about the write, even if there is no error.
This information could be made optional based on a flag for the write command like:
> runCommand({write-command:"ns", args:{}, replicationStats:true}); { "ok" : 1, "n" : 1, "replication" : { "writtenTo": {...}, "lastOp" : Timestamp(1410874677, 2), "electionId" : ObjectId("54183d104e7e3b1d24ab296a")} }
Note: lastOp and electionId are already returned in the response at the top.
- is duplicated by
-
SERVER-15267 Add more information to writeconcern timeout error
- Closed
- is related to
-
SERVER-4073 getLastError should return the members that the write has been replicated to
- Closed