[
https://issues.apache.org/jira/browse/HBASE-22416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16840599#comment-16840599
]
Sean Mackrory commented on HBASE-22416:
---------------------------------------
+1 (non-binding) from me on the current patch. I'm not opposed to
preferIPv4Stack either - there's plenty of that already in the Hadoop ecosystem
- but I'd prefer not to mess with the network I'm on enough that I can get IPv6
is enabled enough to try but not set up enough to actually work - so I won't
pretend to have tested such a patch :)
> 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: Minor
> Labels: HBOSS
> 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)
