[jira] [Updated] (ACCUMULO-3340) MiniAccumuloCluster takes a long time to start when IPv6 is enabled

["Corey J. Nolet (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ACCUMULO-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Corey J. Nolet updated ACCUMULO-3340:
-------------------------------------
    Fix Version/s:     (was: 1.6.2)
                   1.6.3

> MiniAccumuloCluster takes a long time to start when IPv6 is enabled
> -------------------------------------------------------------------
>
>                 Key: ACCUMULO-3340
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3340
>             Project: Accumulo
>          Issue Type: Bug
>          Components: mini
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>             Fix For: 1.5.3, 1.7.0, 1.6.3
>
>          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 {{127.0.0.1}}.
> Additionally, a configuration option could be added to MiniAccumuloConfig to be able to configure the bind address, and simply default to {{127.0.0.1}}.
> 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
(v6.3.4#6332)