Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
HBase >> mail # user >> Problem on setting up hbase cluster in a special environment


+
Yu Li 2012-12-07, 11:59
+
Yu Li 2012-12-07, 12:01
+
Harsh J 2012-12-07, 13:12
+
Yu Li 2012-12-07, 20:17
Copy link to this message
-
Re: Problem on setting up hbase cluster in a special environment
Hi Harsh,

Thanks a lot for your reply, it's  . For #2, I double checked and found the
patches(HADOOP-8154 and HADOOP-7806) are also in branch-1, only that it
exists in hadoop release later than(including) 1.1.0, we're using
hadoop-1.0.4 here, so it's not included.

On 7 December 2012 21:12, Harsh J <[EMAIL PROTECTED]> wrote:

> Hi,
>
> 1. Too bad that you can't change the hostname to be an actual meaningful
> one. I would not consider a node in the network a proper one if it does not
> define a usable default hostname.
> 2. Virtual NIF name support (iface:sub-iface format) is available in Hadoop
> 2.x based releases. Perhaps that may help a bit.
> 3. Reverse DNS is essential I would say, as there are a few places I think
> that stores IPs instead of hostnames, and may need to do a lookup at some
> point. Not 100% sure if the lack of this will work across the stack.
>
> Looks to me like your networked condition is setup in a pretty non-standard
> way. Please do contact your network administrators to set things right. A
> sane network setup is necessary for a pain-free experience in a distributed
> system.
>
>
> On Fri, Dec 7, 2012 at 5:29 PM, Yu Li <[EMAIL PROTECTED]> wrote:
>
> > Dear all,
> >
> > We have met with some problem setting up hbase cluster in one special
> > environment, as described below:
> >
> > 1) The output of "hostname -i" on hbase master node is 127.0.0.1, and we
> > don't have sudo rights to change hostname of the machine
> > 2) The network interface we want hbase to use is virtual, with name like
> > "eth1:0", which cannot be recognized by the NetworkInterface#getByName
> > method, thus setting the "hbase.regionserver.dns.interface" to "eth1:0"
> > doesn't work
> > 3) There's no reverse DNS setup in the environment
> >
> > I noticed on the Reference Guide that "Both forward and reverse DNS
> > resolving must work in versions of HBase previous to 0.92.0", so I guess
> > there must have been some work-around in the env w/o reverse DNS,
> correct?
> > Are there any suggestions on how to setup the hbase cluster in this
> > environment? Thanks in advance, and look forward to your reply.
> >
> >
> > --
> > Best Regards,
> > Li Yu
> >
>
>
>
> --
> Harsh J
>

--
Best Regards,
Li Yu