[SERVER-48717] Implement the persist/recover functionalities of the VectorClock Created: 11/Jun/20 Updated: 09/Aug/20 Resolved: 16/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Pierlauro Sciarelli |
| Resolution: | Done | Votes: | 0 |
| Labels: | PM-1645-Milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Sprint: | Sharding 2020-07-13, Sharding 2020-06-29, Sharding 2020-07-27 | ||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||
| Description |
|
Per this section of the design, the VectorClock needs to expose ability to persist its state durably to disk and recover it so that any decision made on a cache can be recovered. Methods to implement:
|
| Comments |
| Comment by Githook User [ 16/Jul/20 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 16/Jul/20 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |