accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2065) Broke log-forwarding with monitor binding to 0.0.0.0
Date Thu, 19 Dec 2013 19:08:07 GMT

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

ASF subversion and git services commented on ACCUMULO-2065:
-----------------------------------------------------------

Commit a480f63958cee884091fa1f0ad3c542fec5c385a in branch refs/heads/1.5.1-SNAPSHOT from [~elserj]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=a480f63 ]

ACCUMULO-2065 Using the hostname for the system running the monitor instead of what was passed
via --address.

The only downside here is if DNS is not set up. However, if DNS is not set up, you're likely
running on a single box, at
which point localhost is all you need anyways.


> Broke log-forwarding with monitor binding to 0.0.0.0
> ----------------------------------------------------
>
>                 Key: ACCUMULO-2065
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2065
>             Project: Accumulo
>          Issue Type: Bug
>          Components: monitor
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Critical
>             Fix For: 1.5.1, 1.6.0
>
>
> In specifying the --address 0.0.0.0 for the monitor, that's also what got placed in ZooKeeper
which means that external services can't forward their logs.
> The easiest is to probably to revert ACCUMULO-1985 changes to pass in the host from conf/monitor,
and then add a new option that will override the address when starting the HTTP server.



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

Mime
View raw message