[
https://issues.apache.org/jira/browse/OAK-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Saurabh updated OAK-3086:
-------------------------------
Attachment: oplog-slice.patch
Attaching [^oplog-slice.patch] which adds {{oak.printOplogSliceCommand}} method
to the api.
This method can be used as follows:
{noformat}
> oak.printOplogSliceCommand("r12345678-0-1")
mongoexport --host 127.0.0.1 --port 27017 --db local --collection oplog.rs
--out oplog.json --query '{"ns" : "oak.nodes", "ts": {"$gte": Timestamp(305409,
1), "$lte": Timestamp(305430, 1)}}'
{noformat}
OR, to provide some custom parameters as:
{noformat}
> oak.printOplogSliceCommand("r12345678-0-1", {filename:"new-oplog.json",
> db:"oak-aem", oplogTimeBuffer:5})
mongoexport --host 127.0.0.1 --port 27017 --db local --collection oplog.rs
--out new-oplog.json --query '{"ns" : "oak-aem.nodes", "ts": {"$gte":
Timestamp(305414, 1), "$lte": Timestamp(305425, 1)}}'
{noformat}
[~chetanm], can you please review?
> [oak-mongo.js] Generate mongoexport command to get a slice of oplog entries
> ---------------------------------------------------------------------------
>
> Key: OAK-3086
> URL: https://issues.apache.org/jira/browse/OAK-3086
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
> Reporter: Vikas Saurabh
> Priority: Minor
> Attachments: oplog-slice.patch
>
>
> During investigation of OAK-3081, the biggest evidence of how the
> inconsistency occurred was in oplog entries around the time the corrupt
> revision was generated.
> It'd nice to have a utility method in oak-mongo.js which generates a
> mongoexport command to extract oplog entries around the time when a given
> revision was made.
> (cc [~mreutegg], [~chetanm])
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
