accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2855) Use hostname lookup for MiniAccumuloCluster ZooKeeper configuration
Date Sat, 07 Jun 2014 20:16:03 GMT


Josh Elser commented on ACCUMULO-2855:

bq. it might be better to extend MAC with a more generic cluster. I think Josh Elser was interested
in doing something like that.

I think for MAC's case, you'd still just want to provide a single hostname/addr to use for
binding since its intent is to run solely on a single host. Things change in a lot of other
ways too when you start thinking about using other deployment systems to programmatically
run a cluster.

bq. 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).

I'd agree here. How about allowing a hostname/IP value to be used for MAC, default it to localhost
so it continues to work as it does now, and then let the resolution happen as the network
is configured? That would keep up from making any weird assumptions and satisfy Bill's original

> Use hostname lookup for MiniAccumuloCluster ZooKeeper configuration
> -------------------------------------------------------------------
>                 Key: ACCUMULO-2855
>                 URL:
>             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

View raw message