You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/01/29 18:13:35 UTC

[jira] [Updated] (SLING-4371) Create 'cluster clocks in sync' health check

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

Stefan Egli updated SLING-4371:
-------------------------------
    Fix Version/s: Discovery Impl 1.0.14

> Create 'cluster clocks in sync' health check
> --------------------------------------------
>
>                 Key: SLING-4371
>                 URL: https://issues.apache.org/jira/browse/SLING-4371
>             Project: Sling
>          Issue Type: Sub-task
>          Components: Extensions, Health Check
>            Reporter: Stefan Egli
>             Fix For: Discovery Impl 1.0.14
>
>
> Write a health-check (probably in the discovery.impl bundle itself?) that checks the newly added 'votedAt' timestamp of each cluster instance and makes sure they don't differ too much. If they do, fail the check. This would be a very simple check to make sysadmins aware that the clocks are not in sync - or for that matter, that there is a problem in the repository, ie that there are too large write-delays between instances hooked to the same repository.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)