[SERVER-13704] write commands handles ClockSkewException differently from legacy writes Created: 23/Apr/14  Updated: 27/Oct/15  Resolved: 01/May/14

Status: Closed
Project: Core Server
Component/s: Write Ops
Affects Version/s: 2.6.0
Fix Version/s: 2.7.0

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-13741 Migrate remaining tests to use write ... Closed
Related
is related to DOCS-3320 Remove getoptime from the docs Closed
Operating System: ALL
Participants:

 Description   

The server used to terminate when it detects ClockSkewException. However, write commands intercepts it and simply set the error field for the response



 Comments   
Comment by Randolph Tan [ 01/May/14 ]

To docs team:

"getoptime" command is now removed

Comment by Githook User [ 01/May/14 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-13704 write commands handles ClockSkewException differently from legacy writes
Branch: master
https://github.com/mongodb/mongo/commit/3fd39a9fe002c4bdd762d7434fb244a5b153b018

Generated at Thu Feb 08 03:32:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.