[SERVER-19736] Add opTime invariant checks when updating cached config server data Created: 03/Aug/15 Updated: 25/Jan/17 Resolved: 17/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.1.6 |
| Fix Version/s: | 3.1.7 |
| Type: | Task | 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: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding 8 08/28/15 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Add a way to remember the opTime of where a config server data is based from. It will then be possible to add sanity checks in the server to make sure that it never tries to overwrite old data over a new one and also make sure that a collection opTime is always newer than the db opTime that owns it. |
| Comments |
| Comment by Githook User [ 17/Aug/15 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: Revert "Revert " This reverts commit e4cecb7d0dcf61cf16cba96414f99fc5ca097727. |
| Comment by Githook User [ 17/Aug/15 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: Revert " This reverts commit 2a0c88b48eb28231b6bfe81b6b717ceafdece0a6. |
| Comment by Githook User [ 14/Aug/15 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: |