You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2014/08/26 07:14:58 UTC
[jira] [Resolved] (ACCUMULO-3054) Improve notion of "health" in
replication servlet
[ https://issues.apache.org/jira/browse/ACCUMULO-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser resolved ACCUMULO-3054.
----------------------------------
Resolution: Fixed
> Improve notion of "health" in replication servlet
> -------------------------------------------------
>
> Key: ACCUMULO-3054
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3054
> Project: Accumulo
> Issue Type: Improvement
> Components: monitor, replication
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 1.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> [~ecn] suggested to me that the replication servlet could be updated to be more clear about what is healthy and what is not. Update the servlet to compute a general measure of "healthy", "potentially unhealthy", and "not healthy at all".
> Generally speaking, we have to temper the amount of replication backlog in with the size of the system we're working against. A backlog of 50 files could be expected when running with 25+ tservers, while 15 files would be indicative of a problem with only 2 tservers.
--
This message was sent by Atlassian JIRA
(v6.2#6252)