Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Sat, 7 Jun 2014 17:00:05 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12718200.1401815779804.87749.1402160405634@arcas>
In-Reply-To: <JIRA.12718200.1401815779804@arcas>
References: <JIRA.12718200.1401815779804@arcas>
Subject: [jira] [Commented] (ACCUMULO-2855) Use hostname lookup for
 MiniAccumuloCluster ZooKeeper configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Christopher Tubbs commented on ACCUMULO-2855:
---------------------------------------------

A lookup attempt could be fine... I just find them to be problematic, because they make too many assumptions, and those assumptions may be completely invalid. Which NIC are you going to use? Which IP, if the NIC has multiple? Which hostname do you use if DNS reports multiple? What if the hostname known locally is not the one used publicly?

Worse, we have to maintain the code that implements these assumptions, while artificially limiting users for whom these assumptions are invalid. And, the invalidity of these assumptions is possibly quite frequent, due to infrastructure like EC2, where users have separate private IP address space and public IP address space, and a DNS that they may have less control over. Of course, we could do both: allow explicit configuration and default to some heuristic... but then, we're adding a lot more complexity and potential for confusion for users that makes debugging harder.

This is why I think software like httpd does it best when they just make it explicitly configurable (as in the Listen and ServerName directives in httpd.conf).

> Use hostname lookup for MiniAccumuloCluster ZooKeeper configuration
> -------------------------------------------------------------------
>
>                 Key: ACCUMULO-2855
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2855
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: mini
>    Affects Versions: 1.5.1, 1.6.0
>            Reporter: Bill Havanki
>            Priority: Trivial
>
> The configuration generated by the MAC for ZooKeeper uses a hardcoded "localhost" for the ZooKeeper process host. It would be better to at least attempt looking up the FQDN, so that processes running on another machine can connect. (Example: using an outside cluster's MapReduce assets)


--
This message was sent by Atlassian JIRA
(v6.2#6252)