jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Valentin Olteanu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-3273) ColdStandby JMX Status
Date Mon, 24 Aug 2015 13:06:46 GMT

     [ https://issues.apache.org/jira/browse/OAK-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Valentin Olteanu updated OAK-3273:
----------------------------------
    Attachment: OAK-3273.patch

> ColdStandby JMX Status 
> -----------------------
>
>                 Key: OAK-3273
>                 URL: https://issues.apache.org/jira/browse/OAK-3273
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: tarmk-standby
>            Reporter: Valentin Olteanu
>            Priority: Minor
>         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)

Mime
View raw message