Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
Reviewed
Description
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
Attachments
Attachments
Issue Links
- relates to
-
HBASE-22149 HBOSS: A FileSystem implementation to provide HBase's required semantics on object stores
- Resolved