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

Switch to Plain View
HBase, mail # user - loss znode


+
Zbierski Christophe 2012-12-13, 10:12
+
Nicolas Liochon 2012-12-13, 12:07
+
Zbierski Christophe 2012-12-13, 12:55
+
Jean-Marc Spaggiari 2012-12-13, 12:58
+
Zbierski Christophe 2012-12-13, 13:09
+
Nicolas Liochon 2012-12-13, 13:34
+
Zbierski Christophe 2012-12-13, 15:08
+
Jean-Marc Spaggiari 2012-12-13, 13:15
+
Zbierski Christophe 2012-12-13, 16:22
+
Jean-Marc Spaggiari 2012-12-13, 16:33
+
Nicolas Liochon 2012-12-13, 16:53
Copy link to this message
-
Re: loss znode
Nick Dimiduk 2012-12-13, 17:07
Hi Christophe,

You need to update all of your configuration, as per the pseudo-distributed
instructions [0]. Specifically, I believe you're missing
the hbase.cluster.distributed property.

-n

[0]: http://hbase.apache.org/book/standalone_dist.html#pseudo

On Thu, Dec 13, 2012 at 5:09 AM, Zbierski Christophe <
[EMAIL PROTECTED]> wrote:

> I added a new ZK server (listening on port 3128),
> And I changed HBase-site.xml :
>
>   <property>
>      <name>hbase.zookeeper.property.clientPort</name>
>      <value>3181</value>
>   </property>
>   <property>
>   <name>hbase.zookeeper.quorum</name>
>   <value>127.0.0.1</value>
>   </property>
>
> And, when I launch 'start-hbase.sh'
> /opt/hbase-0.94.3/bin]# start-hbase.sh
> starting master, logging to
> /opt/hbase-0.94.3/bin/../logs/hbase-tof-master-W30596-lnx.out
> Could not start ZK at requested port of 3181.  ZK was started at port:
> 3182.  Aborting as clients (e.g. shell) will not be able to find this ZK
> quorum.
>
> Log file :
> 2012-12-13 13:58:35,053 INFO
> org.apache.zookeeper.server.NIOServerCnxnFactory: binding to port
> 0.0.0.0/0.0.0.0:3181
> 2012-12-13 13:58:35,054 DEBUG
> org.apache.hadoop.hbase.zookeeper.MiniZooKeeperCluster: Failed binding ZK
> Server to client port: 3181
> 2012-12-13 13:58:35,054 INFO
> org.apache.zookeeper.server.NIOServerCnxnFactory: binding to port
> 0.0.0.0/0.0.0.0:3182
>
> I think the server wants to start ZK on the same port.
>
>
> -----Message d'origine-----
> De : Jean-Marc Spaggiari [mailto:[EMAIL PROTECTED]]
> Envoyé : jeudi 13 décembre 2012 13:58
> À : [EMAIL PROTECTED]
> Objet : Re: loss znode
>
>
> Hi Christophe,
>
> What do you mean by " I can not do it "?
>
> Is it giving you an error? You don't know the steps? You don't have the
> rights?
>
> --
> JM
>
> 2012/12/13, Zbierski Christophe <[EMAIL PROTECTED]>:
> > Yes, I tried, but I can not do it ... :(
> >
> > -----Message d'origine-----
> > De : Nicolas Liochon [mailto:[EMAIL PROTECTED]] Envoyé : jeudi 13
> > décembre 2012 13:07 À : [EMAIL PROTECTED] Objet : Re: loss znode
> >
> > After looking at the code, it's seems that it's done by the mini zk
> > cluster: the directory is deleted at startup.
> > This is because the default mode (non distributed, all threads in a
> > single
> > process) uses a specific piece of code (this mini* stuff). As it's for
> > tests, it ensures that there is no remains from previous start/stop.
> >
> > You can use a separated ZK instance if you want to keep the data
> > between the runs.
> >
> >
> >
> > On Thu, Dec 13, 2012 at 11:12 AM, Zbierski Christophe <
> > [EMAIL PROTECTED]> wrote:
> >
> >> Hello, I have a problem with zookeeper.
> >> I have a standalone HBase server, and I create a none  ephemeral
> >> znode (to manage my configuration).
> >> When I started up again HBase, this znode no longer exists, and hbase
> >> working properly (event after the restart).
> >>
> >> My hbase version is 0.94.3
> >>
> >> hbase-site.xml :
> >> ...
> >>   <property>
> >>           <name>hbase.zookeeper.property.dataDir</name>
> >>           <value>/DATA/zookeeper</value>
> >>   </property>
> >>
> >>
> >> Christophe Z.
> >>
> >> ________________________________
> >>
> >> Ce message et les pi?ces jointes sont confidentiels et r?serv?s ?
> >> l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g?
> >> par le secret professionnel. Si vous recevez ce message par erreur,
> >> merci d'en avertir imm?diatement l'exp?diteur et de le d?truire.
> >> L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la
> >> responsabilit? d'Atos ne pourra ?tre recherch?e quant au contenu de
> >> ce message. Bien que les meilleurs efforts soient faits pour
> >> maintenir cette transmission exempte de tout virus, l'exp?diteur ne
> >> donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait
> >> ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.
> >>
> >> This e-mail and the documents attached are confidential and intended