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

Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2017/12/31 09:05:00 UTC

[jira] [Commented] (ACCUMULO-4776) Broke log-forwarding with monitor binding to 0.0.0.0

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

Christopher Tubbs commented on ACCUMULO-4776:
---------------------------------------------

I'm a bit confused by the history of this. In which versions is this broken? Is this something we can fix in 2.0.0 with (perhaps) better config options for explicitly setting the bind address? Or do we need to address it in earlier versions, too?

> Broke log-forwarding with monitor binding to 0.0.0.0
> ----------------------------------------------------
>
>                 Key: ACCUMULO-4776
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4776
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: John Vines
>             Fix For: 2.0.0
>
>
> ACCUMULO-2065 fixed this by explicitly using the local host name as the hostname to advertise. This was rolled back in ACCUMULO-4032 because the 2065 change broke the ability to specific which specific name/ip to bind to. This means that log forwarding does not work in clusters using ACCUMULO_MONITOR_BIND_ALL (originally introduced under ACCUMULO-1985)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)