[jira] [Commented] (HBASE-22416) HBOSS: unit tests fail with ConnectionLoss when IPv6 enabled and not set up locally

["Josh Elser (JIRA)" <ji...@apache.org>]

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

Josh Elser commented on HBASE-22416:
------------------------------------

[~wchevreuil], [~mackrorysd], what do you think of this? I'm avoiding setting a surefire-plugin wide rule to force ipv4. On my laptop, it looks like the initial attempt to connect over ipv6 takes ~5 seconds, but is a bit faster in subsequent attempts.

> HBOSS: unit tests fail with ConnectionLoss when IPv6 enabled and not set up locally
> -----------------------------------------------------------------------------------
>
>                 Key: HBASE-22416
>                 URL: https://issues.apache.org/jira/browse/HBASE-22416
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Major
>             Fix For: hbase-filesystem-1.0.0-alpha1
>
>         Attachments: HBASE-22416.001.patch
>
>
> I've seen that the HBOSS unit tests will fail for me with a ConnectionLoss exception. This is resolved when I force ipv4. My hunch is that we don't block for curator to become connected, and because of my local setup, the ipv6 lookup happens first and has to time-out. The test starts running but Curator hasn't yet become connected, so we fail with a ConnectionLoss in the test itself.
> We should wait for Curator to become connected and maybe add {{-Djava.net.preferIPv4Stack=true}} to surefire opts



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)