Better manage standalone setups on Ubuntu, the 127.0.1.1 issue
--------------------------------------------------------------
Key: HBASE-5004
URL: https://issues.apache.org/jira/browse/HBASE-5004
Project: HBase
Issue Type: Improvement
Affects Versions: 0.90.4
Reporter: Jean-Daniel Cryans
Fix For: 0.92.0, 0.94.0, 0.90.6
Numerous times users have come with issues setting up HBase on Ubuntu because
it has the 127.0.1.1 line messing everything. Here's an example:
{quote}
2011-12-10 00:18:24,312 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Serving as
localhost,33371,1323476299775, RPC listening on /127.0.1.1:33371,
sessionid=0x1342555adc90002
...
2011-12-10 00:18:27,135 DEBUG org.apache.hadoop.hbase.master.AssignmentManager:
Assigning region -ROOT-,,0.70236052 to localhost,33371,1323476299775
2011-12-10 00:18:27,135 DEBUG org.apache.hadoop.hbase.master.ServerManager: New
connection to localhost,33371,1323476299775
2011-12-10 00:18:27,155 INFO org.apache.hadoop.ipc.HbaseRPC: Server at
/127.0.0.1:33371 could not be reached after 1 tries, giving up.
2011-12-10 00:18:27,156 WARN org.apache.hadoop.hbase.master.AssignmentManager:
Failed assignment of -ROOT-,,0.70236052 to
serverName=localhost,33371,1323476299775, load=(requests=0, regions=0,
usedHeap=23, maxHeap=983), trying to assign elsewhere instead; retry=0
org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed setting up
proxy interface org.apache.hadoop.hbase.ipc.HRegionInterface to
/127.0.0.1:33371 after attempts=1
{quote}
We should have a special check in standalone mode to make sure we won't fall
into that trap and then print a useful error message that would hopefully
appear on the command line.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
