Hi there. You generally don't want to run with 2 clusters like (HBase on one, HDFS on the other) that because your regions have 0% locality.
For more information on this topic, seeĊ . http://hbase.apache.org/book.html#regions.arch.locality On 10/17/12 12:19 PM, "Richard Tang" <tristartom.t...@gmail.com> wrote: >Hello, everyone, >I have problems using hbase based on unqualified hostname. My ``hbase`` >runs in a cluster and ``hdfs`` on another cluster. While using fully >qualified name on ``hbase``, for properties like ``hbase.rootdir`` and >``hbase.zookeeper.quorum``, there is no problem. But when I change them to >be shorter unqualified names, like ``node4`` and ``node2``, (which are >resolved to local ip address by ``/etc/hosts``, like ``10.0.0.8``), the >hbase cluster begin to throw ``Connect refused`` messages. Anyone >encounter >same problem here?What is the possible reason behind all theses? Thanks. >Regards, >Richard