[jira] [Commented] (KAFKA-2237) zookeeper chroot path should be created on broker startup
[ https://issues.apache.org/jira/browse/KAFKA-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569752#comment-14569752 ] Adrian Muraru commented on KAFKA-2237: -- False alarm, yeah on 0.8.2 it seems to work fine. It was 0.8.1 where this was seen. Let's close was Cannot Reproduce or smth. Thanks > zookeeper chroot path should be created on broker startup > - > > Key: KAFKA-2237 > URL: https://issues.apache.org/jira/browse/KAFKA-2237 > Project: Kafka > Issue Type: Bug > Components: config >Reporter: Adrian Muraru > > Right now when a chroot path is used to maintain zk metadata and not > available at startup - broker fails to start. > Would it make sense to have it automatically created by the broker itself if > it doesn't exist? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KAFKA-2237) zookeeper chroot path should be created on broker startup
[ https://issues.apache.org/jira/browse/KAFKA-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569672#comment-14569672 ] Ewen Cheslack-Postava commented on KAFKA-2237: -- KAFKA-404 which is pretty old now, so if you're relatively up to date this should work. Can you describe the steps you take to reproduce this? > zookeeper chroot path should be created on broker startup > - > > Key: KAFKA-2237 > URL: https://issues.apache.org/jira/browse/KAFKA-2237 > Project: Kafka > Issue Type: Bug > Components: config >Reporter: Adrian Muraru > > Right now when a chroot path is used to maintain zk metadata and not > available at startup - broker fails to start. > Would it make sense to have it automatically created by the broker itself if > it doesn't exist? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KAFKA-2237) zookeeper chroot path should be created on broker startup
[ https://issues.apache.org/jira/browse/KAFKA-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569586#comment-14569586 ] Adrian Muraru commented on KAFKA-2237: -- Do you know by chance the JIRA id where this was implemented? > zookeeper chroot path should be created on broker startup > - > > Key: KAFKA-2237 > URL: https://issues.apache.org/jira/browse/KAFKA-2237 > Project: Kafka > Issue Type: Bug > Components: config >Reporter: Adrian Muraru > > Right now when a chroot path is used to maintain zk metadata and not > available at startup - broker fails to start. > Would it make sense to have it automatically created by the broker itself if > it doesn't exist? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KAFKA-2237) zookeeper chroot path should be created on broker startup
[ https://issues.apache.org/jira/browse/KAFKA-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569583#comment-14569583 ] Adrian Muraru commented on KAFKA-2237: -- [~nehanarkhede] I'm on 0.8.2 branch > zookeeper chroot path should be created on broker startup > - > > Key: KAFKA-2237 > URL: https://issues.apache.org/jira/browse/KAFKA-2237 > Project: Kafka > Issue Type: Bug > Components: config >Reporter: Adrian Muraru > > Right now when a chroot path is used to maintain zk metadata and not > available at startup - broker fails to start. > Would it make sense to have it automatically created by the broker itself if > it doesn't exist? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KAFKA-2237) zookeeper chroot path should be created on broker startup
[ https://issues.apache.org/jira/browse/KAFKA-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569532#comment-14569532 ] Neha Narkhede commented on KAFKA-2237: -- [~amuraru] My understanding is that we have fixed this though I'm not sure if a released version has the fix. Would you mind clarifying which version of Kafka you used and if you still see this on trunk? > zookeeper chroot path should be created on broker startup > - > > Key: KAFKA-2237 > URL: https://issues.apache.org/jira/browse/KAFKA-2237 > Project: Kafka > Issue Type: Bug > Components: config >Reporter: Adrian Muraru > > Right now when a chroot path is used to maintain zk metadata and not > available at startup - broker fails to start. > Would it make sense to have it automatically created by the broker itself if > it doesn't exist? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
