Hi there- re: "From what I have understood, these properties are not for Hbase but for the Hbase client which we write. They tell the client where to look for ZK."
Yep. That's how it works. Then the client looks up ROOT/META and then the client talks directly to the RegionServers. http://hbase.apache.org/book.html#client On 11/27/12 8:52 AM, "Mohammad Tariq" <donta...@gmail.com> wrote: >Hello Matan, > > From what I have understood, these properties are not for Hbase but >for the Hbase client which we write. They tell the client where to look >for >ZK. > >Hmaster registers its address with ZK. And from there client will come to >know where to look for Hmaster. And if the Hmaster registers its address >as >'localhost', the client will take it as the 'localhost', which is client's >'localhost' and not the 'localhost' where Hmaster is running. So, if you >have the IP and hostname of the Hmaster in your /etc/hosts file the client >can reach that machine without any problem as there is proper DNS >resolution available. > >But this just is what I think. I need approval from the heavyweights. > >Stack sir?? > > > >Regards, > Mohammad Tariq > > > >On Tue, Nov 27, 2012 at 5:57 PM, matan <ma...@cloudaloe.org> wrote: > >> Thanks guys, >> >> Excuse my ignorance, but having sort of agreed that the configuration >>that >> determines which-server-should-be-contacted-for-what is on the HBase >> server, I am not sure how any of the practical suggestions made should >> solve the issue, and enable connecting from a remote client. >> >> Let me delineate - setting /etc/hosts on my client side seems in this >> regard not relevant in that view. And the other suggestion for >> hbase-site.xml configuration I have already got covered, as my client >>code >> successfully connects to zookeeper (the configuration properties >>mentioned >> on this thread are zookeeper specific according to my interpretation of >> documentation, I don't directly see how they should solve the problem). >> Perhaps Mohammad you can explain why those zookeeper properties relate >>to >> how the master references itself towards zookeeper? >> >> Should I take it from St.Ack that there is currently no way to specify >>the >> master's remotely accessible server/ip in the HBase configuration? >> >> Anyway, my HBase server's /etc/hosts has just one line now, in case it >>got >> lost on the thread - >> 127.0.0.1 localhost 'server-name'. Everything works fine on the HBase >> server itself, the same client code runs perfectly there. >> >> Thanks again, >> Matan >> >> On Mon, Nov 26, 2012 at 10:15 PM, Tariq [via Apache HBase] < >> ml-node+s679495n4034419...@n3.nabble.com> wrote: >> >> > Hello Nicolas, >> > >> > You are right. It has been deprecated. Thank you for updating my >> > knowledge base..:) >> > >> > Regards, >> > Mohammad Tariq >> > >> > >> > >> > On Tue, Nov 27, 2012 at 12:17 AM, Nicolas Liochon <[hidden email]< >> http://user/SendEmail.jtp?type=node&node=4034419&i=0>> >> > wrote: >> > >> > > Hi Mohammad, >> > > >> > > Your answer was right, just that specifying the master address is >>not >> > > necessary (anymore I think). But it does no harm. >> > > Changing the /etc/hosts (as you did) is right too. >> > > Lastly, if the cluster is standalone and accessed locally, having >> > localhost >> > > in ZK will not be an issue. However, it's perfectly possible to >>have a >> > > standalone cluster accessed remotely, so you don't want to have the >> > master >> > > to write "I'm on the server named localhost" in this case. I expect >>it >> > > won't be an issue for communications between the region servers or >>hdfs >> > as >> > > they would be all on the same "localhost"... >> > > >> > > Cheers, >> > > >> > > Nicolas >> > > >> > > On Mon, Nov 26, 2012 at 7:16 PM, Mohammad Tariq <[hidden email]< >> http://user/SendEmail.jtp?type=node&node=4034419&i=1>> >> > >> > > wrote: >> > > >> > > > what >> > > >> > >> > >> > ------------------------------ >> > If you reply to this email, your message will be added to the >>discussion >> > below: >> > >> > >> >>http://apache-hbase.679495.n3.nabble.com/Connecting-to-standalone-HBase-f >>rom-a-remote-client-tp4034362p4034419.html >> > To unsubscribe from Connecting to standalone HBase from a remote >> client, click >> > here< >> >>http://apache-hbase.679495.n3.nabble.com/template/NamlServlet.jtp?macro=u >>nsubscribe_by_code&node=4034362&code=bWF0YW5AY2xvdWRhbG9lLm9yZ3w0MDM0MzYy >>fC0xMDg3NTk1Njc3 >> > >> > . >> > NAML< >> >>http://apache-hbase.679495.n3.nabble.com/template/NamlServlet.jtp?macro=m >>acro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namesp >>aces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view. >>web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemai >>l.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3 >>Aemail.naml >> > >> > >> >> >> >> >> -- >> View this message in context: >> >>http://apache-hbase.679495.n3.nabble.com/Connecting-to-standalone-HBase-f >>rom-a-remote-client-tp4034362p4034439.html >> Sent from the HBase User mailing list archive at Nabble.com. >>
