I'm trying to feel-out if auto creating the broker's registration path on server start up would be wanted as a code contribution.
How do the maintainers feel about:
1. Having configurable server parameter:
auto.create.chroot = true | false
2. If (1) is set to true, the chroot would be create automatically in the case that the it is missing from zookeeper, and the server would start up normal.
If the maintainers are OK with this idea I'll code it up, it would solve a use case we have at my work, and I would send in a patch or follow any contribution process given. Right now if you specify zookeeper.connect as:
and /chroot/path does not exist in zookeeper, the server does not operate. -Marek
I don't think its too much to ask people to create their ZK paths: zkCli.sh -server localhost:2181 create /kafka kafka
Asking a ZK application to use a non-existent chroot is like asking tar to extract to a non-existent directory. An error is appropriate. I think the fix here is to give a better error than the very unhelpful/cryptic "Path length must be > 0" (https://issues.apache.org/jira/browse/KAFKA-294)
On 11/13/13 11:13 PM, marek wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext