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

["John Vines (JIRA)" <ji...@apache.org>]

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

John Vines commented on ACCUMULO-4776:
--------------------------------------

Been broken since 1.6.5, 1.7.1, and 1.8.0 (can't put that in affects versions, someone seems to have deleted released versions from our list)

Simply put, ACCUMULO-1985 requested the ability to have hte monitor bind on all interfaces. It wasn't a complete fix that was addressed in ACCUMULO-2065. That means this feature existed since 1.5.1 and 1.6.0. But then it was broken by ACCUMULO-4032, affecting the versions I listed at the start.

> 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
>    Affects Versions: 1.6.6, 1.7.2, 1.8.0
>            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)