e.finishSetup(HTable.java:234)
> at org.apache.hadoop.hbase.client.HTable.(HTable.java:174)
> at org.apache.hadoop.hbase.client.HTable.(HTable.java:133)
> at com.samsung.HBase.DBMain.putData(DBMain.java:32)
> at com.samsung.HBase.DBMain.main(DBMain.java:17)
>
> Please help me...
>
>
>
>
> --
> View this message in context:
> http://apache-hbase.679495.n3.nabble.com/Connecting-to-standalone-HBase-from-a-remote-client-tp4034362p4038027.html
> Sent from the HBase User mailing list archive at Nabble.com.
>
context:
http://apache-hbase.679495.n3.nabble.com/Connecting-to-standalone-HBase-from-a-remote-client-tp4034362p4038027.html
Sent from the HBase User mailing list archive at Nabble.com.
oo.
>>>>>>>> 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
>>>
t;> >
> > > >> >
> > > >> > On Tue, Nov 27, 2012 at 12:17 AM, Nicolas Liochon <[hidden
> email]<
> > > >> http://user/SendEmail.jtp?type=node&node=4034419&i=0>>
> > > >> > wrote:
> > > >
ote:
> > >> >
> > >> > > Hi Mohammad,
> > >> > >
> > >> > > Your answer was right, just that specifying the master address is
> > >>not
> > >> > > necessary (anymore I think). But it does no
ed 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,
&g
egion 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=4034
node&node=4034419&i=1>>
>
> > wrote:
> >
> > > what
> >
>
>
> ----------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-hb
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 wrote:
> Hi Mohammad,
>
> Your answer was right, just that specifying the master address is not
> necessary (
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, i
I was facing the same issue few months ago, but adding the above
specified three properties in my client and IP+Hostname of the machines in
my /etc/hosts worked for me. Is is OK? Another question, if HBase is
running in pseudo mode, then what's the harm in using localhost in
/conf/regionserver
On Mon, Nov 26, 2012 at 9:42 AM, Nicolas Liochon wrote:
> We would detect it and stop properly. It's true even in standalone mode:
> one may want to launch a standalone cluster and connects remotely to it.
>
I made https://issues.apache.org/jira/browse/HBASE-7219 for now.
St.Ack
We would detect it and stop properly. It's true even in standalone mode:
one may want to launch a standalone cluster and connects remotely to it.
On Mon, Nov 26, 2012 at 6:38 PM, Stack wrote:
> distributed, write other than localhost to zk?
> St.Ack
>
Hello Matan,
Did it work?If not, add these properties in your hbase-site.xml file
and see if it works for you.
hbase.zookeeper.quorum
ZH-HOST_MACHINE
hbase.zookeeper.property.clientPort
2181
hbase.zookee
On Mon, Nov 26, 2012 at 7:28 AM, Nicolas Liochon wrote:
> Yes, it's not useful to set the master address in the client. I suppose it
> was different a long time ago, hence there are some traces on different
> documentation.
> The master references itself in ZooKeeper. So if the master finds itself
Yes, it's not useful to set the master address in the client. I suppose it
was different a long time ago, hence there are some traces on different
documentation.
The master references itself in ZooKeeper. So if the master finds itself to
be "locahost", ZooKeeper will contain "locahost", and the cli
;>> could not be reached after 1 tries, giving up.
> >>> 12/11/25 22:26:36 INFO ipc.HBaseRPC: Server at localhost/
> 127.0.0.1:58063
> >>> could not be reached after 1 tries, giving up.
> >>> 12/11/25 22:26:54 INFO ipc.HBaseRPC: Server at localhost/
> 127.0.0
ava:133)
at HelloWorld.main(HelloWorld.java:30)
Thanks!
matan
--
View this message in context:
http://apache-hbase.679495.n3.nabble.com/Connecting-to-standalone-HBase-from-a-remote-client-tp4034362.html
Sent from the HBase User mailing list archive at Nabble.com.
18 matches
Mail list logo
