accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3340) MiniAccumuloCluster takes a long time to start when IPv6 is enabled
Date Mon, 08 Dec 2014 19:17:13 GMT


Josh Elser commented on ACCUMULO-3340:

Trivially, we can force IPv4 by including "". Verified that
this does the trick for me. I think we're still doing this in the default configuration files
we provide, so it's likely reasonable.

bq. This would also probably be solved by ACCUMULO-1549.

And, since I just closed ACCUMULO-1549 as "Won't Fix" yesterday, I dug through TestingServer(Main)
and I didn't see anything where curator is actively disabling IPv6 much less doing anything
else than we aren't already doing for configuration and startup (their stop logic is better
as it reflects to get at the ZK internal servers). Maybe you know something more than me here,

> MiniAccumuloCluster takes a long time to start when IPv6 is enabled
> -------------------------------------------------------------------
>                 Key: ACCUMULO-3340
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: mini
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>             Fix For: 1.5.3, 1.6.2, 1.7.0
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
> ZooKeeper, by default binds to all interfaces. This can cause issues, and can be quite
slow when IPv6 is enabled. MiniAccumuloCluster can set the {{clientPortAddress}} explicitly
in the {{zoo.cfg}} file to ensure it binds to the IPv4 loopback on the localhost {{}}.
> Additionally, a configuration option could be added to MiniAccumuloConfig to be able
to configure the bind address, and simply default to {{}}.
> Another option to pursue is any JVM settings that might restrict ZooKeeper to IPv4 only
during the build tests.

This message was sent by Atlassian JIRA

View raw message