accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2334) Lacking fallback when ACCUMULO_LOG_HOST isn't set
Date Fri, 07 Feb 2014 22:33:21 GMT

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

Josh Elser commented on ACCUMULO-2334:
--------------------------------------

In implementing this, I came to the conclusion that it's actually a bit cleaner to just remove
ACCUMULO_LOG_HOST completely and use zookeeper for monitor log-forwarding discovery.

Made a review for the changes just to get some extra eyes on it, but I feel pretty comfortable
with the changes.

> Lacking fallback when ACCUMULO_LOG_HOST isn't set
> -------------------------------------------------
>
>                 Key: ACCUMULO-2334
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2334
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.5.0
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.5.1, 1.6.0
>
>
> For log-forwarding, if ACCUMULO_LOG_HOST is not set, the code falls back to using the
hostname for localhost.
> We already have an address for the monitor in ZK; we should use that instead when populated.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message