You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2020/02/08 00:11:00 UTC

[jira] [Updated] (HBASE-23765) [JDK11] unable to communicate with localhost when setting up Kerberos-related tests

     [ https://issues.apache.org/jira/browse/HBASE-23765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Dimiduk updated HBASE-23765:
---------------------------------
    Summary: [JDK11] unable to communicate with localhost when setting up Kerberos-related tests  (was: [JDK11] Use 127.0.0.1 instead of localhost when setting up Kerberos-related tests)

> [JDK11] unable to communicate with localhost when setting up Kerberos-related tests
> -----------------------------------------------------------------------------------
>
>                 Key: HBASE-23765
>                 URL: https://issues.apache.org/jira/browse/HBASE-23765
>             Project: HBase
>          Issue Type: Task
>          Components: test
>            Reporter: Josh Elser
>            Priority: Minor
>
> [~ndimiduk] gave an ask over on HBASE-23760 to change some of the Hadoop-level configuration properties around secure cluster setup from localhost to 127.0.0.1. He and [~bharathv] have been chasing some issues with ZooKeeper and not having a resolution of localhost to 127.0.0.1.
> Before I start making a change, how sure are we that this is an issue? Assuming that it's the nightlies that we see these on, how about we make a change to increase the krb5 and spnego debugging to see if we aren't resolving names properly?
> There might be a debug property for DNS lookups in Java too.... maybe?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)