[ https://issues.apache.org/jira/browse/HBASE-23796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Robert Miller resolved HBASE-23796. ---------------------------------------- Resolution: Won't Fix This was helpful to me in getting more successful test runs outside of docker, but in recent days, branch-2 can actually pass for me a decent percentage of runs without this change or Docker, so I'm not sure how valuable any of this remaining is. Hadoop auto looks up the hostname regardless of this setting a lot and that appears very slow in my env when happening a lot concurrently and so trying to get out of docker to perform like in docker in my case doesn't seem easily attainable. In docker it is. > Consider using 127.0.0.1 instead of localhost and binding to 127.0.0.1 as > well. > ------------------------------------------------------------------------------- > > Key: HBASE-23796 > URL: https://issues.apache.org/jira/browse/HBASE-23796 > Project: HBase > Issue Type: Test > Reporter: Mark Robert Miller > Priority: Minor > > This is perhaps controversial, but there are a variety of problems with > counting on dns hostname resolution, especially for locahost. > > # It can often be slow, slow under concurrency, or slow under specific > conditions. > # It can often not work at all - when on a VPN, with weird DNS hijacking > hi-jinks, when you have a real hostname for you machines, a custom /etc/hosts > file, OS's run their own local/funny DNS server services. > # This makes coming to HBase for new devs a hit or miss experience and if > you miss, dealing with an diagnosing the issues is a large endeavor and not > straight forward or transparent. > # 99% of the difference doesn't matter in most cases - except that > 127.0.0.1 works and is fast pretty much universally. -- This message was sent by Atlassian Jira (v8.3.4#803005)