[jira] [Updated] (OAK-2113) TarMK cold standby: ensure client integrity
[ https://issues.apache.org/jira/browse/OAK-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-2113: --- Labels: resilience (was: ) > TarMK cold standby: ensure client integrity > > > Key: OAK-2113 > URL: https://issues.apache.org/jira/browse/OAK-2113 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Manfred Baedke >Priority: Minor > Labels: resilience > > TarMK cold standby needs measures to ensure the integrity of each segment on > the slave and that all segments that are reachable on the master from a given > segment are available on the slave. > To ensure the integrity of a given segment on the slave, we can just use the > checksum stored in the segment, so there is no need to change the > communication protocol for this. > To ensure that all segments that are reachable from a given segment are the > same on the master and on the slave, we need a new request to calculate a > suitable checksum on the master and send it back to the slave. > If missing or broken segments are detected, the slave will pull them from the > master again. > Both measures combined should be scheduled to run regularly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-2113) TarMK cold standby: ensure client integrity
[ https://issues.apache.org/jira/browse/OAK-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-2113: --- Component/s: (was: segmentmk) segment-next > TarMK cold standby: ensure client integrity > > > Key: OAK-2113 > URL: https://issues.apache.org/jira/browse/OAK-2113 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-next >Reporter: Manfred Baedke >Priority: Minor > > TarMK cold standby needs measures to ensure the integrity of each segment on > the slave and that all segments that are reachable on the master from a given > segment are available on the slave. > To ensure the integrity of a given segment on the slave, we can just use the > checksum stored in the segment, so there is no need to change the > communication protocol for this. > To ensure that all segments that are reachable from a given segment are the > same on the master and on the slave, we need a new request to calculate a > suitable checksum on the master and send it back to the slave. > If missing or broken segments are detected, the slave will pull them from the > master again. > Both measures combined should be scheduled to run regularly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
