You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2012/04/24 18:43:33 UTC

[jira] [Commented] (ACCUMULO-558) gc should shutdown non-communicative loggers

    [ https://issues.apache.org/jira/browse/ACCUMULO-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260695#comment-13260695 ] 

Keith Turner commented on ACCUMULO-558:
---------------------------------------

The communcation problem could be temporary.  A tablet server should probably not keep trying to use a logger it can not communicate with.  Could blacklist it temporarily.  
                
> gc should shutdown non-communicative loggers
> --------------------------------------------
>
>                 Key: ACCUMULO-558
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-558
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: gc
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>             Fix For: 1.5.0
>
>
> The configuration on a single server was different than the rest of the system.  This causes it to be unable to talk to the rest of the cluster, which is a feature.  But, since it still advertises itself in zookeeper, everyone is trying to use it.  The master will kill a tablet server, but nobody is monitoring the loggers for health.  The gc could do it, since it periodically sweeps all the loggers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira