You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2014/11/17 19:31:35 UTC

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

Christopher Tubbs created ACCUMULO-3340:
-------------------------------------------

             Summary: 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
            Reporter: Christopher Tubbs
            Assignee: Christopher Tubbs
             Fix For: 1.5.3, 1.6.2, 1.7.0


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)