[SERVER-15948] Fast OplogStart mechanism for storage engines supporting arbitrary DiskLocs Created: 04/Nov/14 Updated: 19/Nov/14 Resolved: 04/Nov/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Storage |
| Affects Version/s: | None |
| Fix Version/s: | 2.8.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Minor Change | ||||
| Participants: | |||||
| Description |
|
This is an internal feature that storage engines can opt into. If they support storing arbitrary keys as the loc in an insert, they can use the "ts" field from oplog entries (using the provided methods to extract the key). This allows replication to ask the storage engine where to look when a secondary tries to fetch oplog entries using a query like {ts: {$gt: OpTime(123, 445)}}. |
| Comments |
| Comment by Githook User [ 04/Nov/14 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: |
| Comment by Githook User [ 04/Nov/14 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: |
| Comment by Githook User [ 04/Nov/14 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: |
| Comment by Githook User [ 04/Nov/14 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Storage engines must opt-in to this functionality. For now, heap1 is the only |
| Comment by Githook User [ 04/Nov/14 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: |