Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # user >> How to create the initial zookeeper chroot path for zk.connect?


Copy link to this message
-
Re: How to create the initial zookeeper chroot path for zk.connect?
Actually, we already have a jira: KAFKA-294.

Thanks,

Jun
On Wed, May 8, 2013 at 4:37 PM, Jason Rosenberg <[EMAIL PROTECTED]> wrote:

> It works if I manually create the chroot first.  But this is a bit
> cumbersome if I want to do an automated roll out to multiple deployments,
> etc....but workable....
>
> Should I file a jira?
>
>
> On Wed, May 8, 2013 at 4:31 PM, Jason Rosenberg <[EMAIL PROTECTED]> wrote:
>
> > I'm seeing this issue with a single node zk instance, on my localhost.
>  If
> > my zkconnect is "localhost:12345", it works...
> >
> > but if I add a chroot, e.g.: "localhost:12345/xyz", I get the same error:
> > java.lang.IllegalArgumentException: Path length must be > 0
> >
> > I also get the error if I do: "locahost:12345,localhost:67890/xyz"
> >
> > Do I actually have to create the chroot manually first?  Or shouldn't it
> > get created automatically?
> >
> > This using 0.8.0 latest.....
> >
> > Is this the same issue others are seeing (I realize previously the issue
> > was with multiple zk hosts).  Does this need a jira?
> >
> > Also, I think the config page for zookeeper.connect really needs to be
> > updated to make explicit that the 'chroot' part only gets added at the
> very
> > end, because it's not clear at all....
> >
> > Jason
> >
> >
> > On Mon, Apr 22, 2013 at 6:46 AM, Ryan Chan <[EMAIL PROTECTED]>
> wrote:
> >
> >> It would be better if there is another configuration directive, e.g.
> >> zk.chroot for the chroot path, currently it is not consistent as we also
> >> need to specify the port for each zookeeper, isn't?
> >>
> >> Anyway, the doc can better explained this situation..
> >>
> >> Thanks anyway!
> >>
> >>
> >> On Sun, Apr 21, 2013 at 11:10 PM, Scott Clasen <[EMAIL PROTECTED]>
> wrote:
> >>
> >> > Since There is only 1 chroot for a zk cluster, if you specified for
> each
> >> > server there would be a potential for error/mismatch
> >> >
> >> > Things would probably go really bad if you had mismatched chroots :)
> >> >
> >> > Sent from my iPhone
> >> >
> >> > On Apr 21, 2013, at 1:34 AM, Ryan Chan <[EMAIL PROTECTED]> wrote:
> >> >
> >> > > Thanks, this solved the problem.
> >> > >
> >> > > But the connection string as "Zk1:2181,zk2:2181,zk3;2181/Kafka",
> seems
> >> > > unintuitive?
> >> > >
> >> > >
> >> > > On Sun, Apr 21, 2013 at 2:29 AM, Scott Clasen <[EMAIL PROTECTED]>
> >> wrote:
> >> > >
> >> > >> Afaik you only put the chroot on the end of the zk conn str...
> >> > >>
> >> > >> Zk1:2181,zk2:2181,zk3;2181/Kafka
> >> > >>
> >> > >> Not
> >> > >>
> >> > >> Zk1:2181/kafka,zk2:2181/Kafka,zk3:2181/Kafka
> >> > >>
> >> > >>
> >> > >> Sent from my iPhone
> >> > >>
> >> > >> On Apr 20, 2013, at 9:03 AM, Neha Narkhede <
> [EMAIL PROTECTED]>
> >> > >> wrote:
> >> > >>
> >> > >>> Please file a bug and mention the Kafka and zookeeper versions
> used
> >> for
> >> > >> the
> >> > >>> test.
> >> > >>>
> >> > >>> Thanks,
> >> > >>> Neha
> >> > >>>
> >> > >>> On Saturday, April 20, 2013, Ryan Chan wrote:
> >> > >>>
> >> > >>>> Hello,
> >> > >>>>
> >> > >>>> Tried, still the same...
> >> > >>>>
> >> > >>>>
> >> > >>>> bin/zkCli.sh -server
> >> zookeeper1:2181,zookeeper2:2181,zookeeper3:2181
> >> > >>>> [zk: zookeeper1,zookeeper2,zookeeper3(CONNECTED) 0]  ls /
> >> > >>>> [testkafka, consumers, brokers, zookeeper]
> >> > >>>> [zk: zookeeper1,zookeeper2,zookeeper3(CONNECTED) 1] rmr
> /testkafka
> >> > >>>> [zk: zookeeper1,zookeeper2,zookeeper3(CONNECTED) 2] create
> >> /testkafka
> >> > ''
> >> > >>>> [zk: zookeeper1,zookeeper2,zookeeper3(CONNECTED) 3] ls /
> >> > >>>> [testkafka, consumers, brokers, zookeeper]
> >> > >>>>
> >> > >>>>
> >> > >>>>
> >> > >>>> And restart Kafka
> >> > >>>>
> >> > >>>> [2013-04-20 09:20:58,336] FATAL Fatal error during
> >> KafkaServerStable
> >> > >>>> startup. Prepare to shutdown (kafka.server.KafkaServerStartable)
> >> > >>>> java.lang.IllegalArgumentException: Path length must be > 0
> >> > >>>> at
> >> > org.apache.zookeeper.common.PathUtils.validatePath(PathUtils.java:48)

 
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB