You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2015/08/24 15:18:46 UTC
[jira] [Resolved] (OAK-3273) ColdStandby make sync start and end
timestamp updates atomic
[ https://issues.apache.org/jira/browse/OAK-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Parvulescu resolved OAK-3273.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.3.5
thanks for the patch [~volteanu]! applied at http://svn.apache.org/r1697383
> ColdStandby make sync start and end timestamp updates atomic
> ------------------------------------------------------------
>
> Key: OAK-3273
> URL: https://issues.apache.org/jira/browse/OAK-3273
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: tarmk-standby
> Reporter: Valentin Olteanu
> Assignee: Alex Parvulescu
> Priority: Minor
> Fix For: 1.3.5
>
> Attachments: OAK-3273.patch
>
>
> OAK-3113 introduced two fields in the ColdStandby MBean: SyncStartTimestamp and SyncEndTimestamp. This is much more useful than the old SecondsSinceLastSuccess, yet, there are situations in which it's hard to interpret them since they are updated independently:
> - it's impossible to correlate the start with the end
> - in case of fail, the start still reflects the failed cycle
> It would be even better if the two would be updated atomically, to reflect the start and end of the last successful cycle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)