[
https://issues.apache.org/jira/browse/ACCUMULO-4776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312471#comment-16312471
]
Christopher Tubbs commented on ACCUMULO-4776:
---------------------------------------------
It looks like Ed and Josh discussed this issue back in 2016, but it fell
through the cracks and nobody made a ticket. Now that we know what needs to be
done, it should be simple enough to apply the strategy in 4588 to the older
branches.
https://lists.apache.org/thread.html/aaae97f3c75416089eeaa7bf7b924023d7cb3c3977e2c837ae02c383@1464746172@%3Cdev.accumulo.apache.org%3E
> 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: 1.7.4, 1.8.2
>
>
> 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)
