accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4776) Broke log-forwarding with monitor binding to
Date Fri, 05 Jan 2018 02:16:00 GMT


Christopher Tubbs commented on ACCUMULO-4776:

It looks like this was already fixed in 2.0 as part of ACCUMULO-4588. If the LogService sees
an address of {{}}, it advertises whatever it can determine from {{InetAddress.getLocalHost().getHostName()}}.

The bug is that the advertisement address is {{}} because we don't have separate configuration
knobs to set the bind address separately from the advertisement address.

The strategy in ACCUMULO-4588 should be backported to 1.7 and 1.8.

> Broke log-forwarding with monitor binding to
> ----------------------------------------------------
>                 Key: ACCUMULO-4776
>                 URL:
>             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

View raw message