[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: |
|
||||||||||||||||
| 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: |