accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3340) MiniAccumuloCluster takes a long time to start when IPv6 is enabled
Date Mon, 17 Nov 2014 20:49:34 GMT

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

Mike Drob commented on ACCUMULO-3340:
-------------------------------------

This would also probably be solved by ACCUMULO-1549.

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

Mime
View raw message