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] [Updated] (ACCUMULO-2078) ACCUMULO_LOG_HOST is incorrectly computed
Date Fri, 20 Dec 2013 22:48:10 GMT

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

Josh Elser updated ACCUMULO-2078:
---------------------------------

    Affects Version/s: 1.4.4
                       1.5.0

> ACCUMULO_LOG_HOST is incorrectly computed
> -----------------------------------------
>
>                 Key: ACCUMULO-2078
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2078
>             Project: Accumulo
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 1.4.4, 1.5.0
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Blocker
>             Fix For: 1.4.5, 1.5.1, 1.6.0
>
>
> I couldn't figure out why I wasn't getting any logforwarding set up on a small cluster.
After verifying that DNS was correctly working for FQDN and hostnames, I dug into how the
remote log host is configured.
> The grep included in all accumulo-env.sh examples will *never* work on a multi-node installation
with the example monitor file. Assuming the user will replace "localhost" with the hostname
of the host running the monitor, this will not work which is extremely misleading.
> The reason is because the grep doesn't exclude any whitespace, so, in o.a.a.s.Accumulo,
the value will be replaced with the hostname for localhost (which will eat all of the logs
intended for the monitor).



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message