accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Havanki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2855) Use hostname lookup for MiniAccumuloCluster ZooKeeper configuration
Date Fri, 06 Jun 2014 21:05:03 GMT

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

Bill Havanki commented on ACCUMULO-2855:
----------------------------------------

The particular use case where this came up was when we were running the integration tests,
but using a "real" cluster's MapReduce instead of relying on the local runner (some of the
ITs run MR jobs). The Accumulo code running over on the task trackers needed to connect to
ZooKeeper, but of course failed due to it being at "localhost".

Allowing explicit configuration sounds great to me, although at that point it doesn't seem
like much farther to permit a lookup attempt to be configured (and, say, fallback to some
default, maybe "localhost"). Thoughts?

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

Mime
View raw message