[SERVER-28158] SnapshotThread should stop using LogicalClock to trigger snapshots Created: 01/Mar/17 Updated: 05/Apr/17 Resolved: 07/Mar/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.5.3 |
| Fix Version/s: | 3.5.5 |
| 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 2017-03-06, Sharding 2017-03-27 | ||||||||
| Participants: | |||||||||
| Description |
|
Since it can advance without any writes. Code in question: Rationale: 0. Secondary is replicated till ts = T9. Also note that the newTimestampNotifier will also need to change to trigger after the actual applied/generated opTime was changed (as opposed to the LogicalClock) |
| Comments |
| Comment by Githook User [ 07/Mar/17 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Note: This is a temporary band aid since the snapshot thread is slated for removal soon. |