[
https://issues.apache.org/jira/browse/SOLR-8378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048441#comment-15048441
]
Jan Høydahl commented on SOLR-8378:
-----------------------------------
This discussion is related to SOLR-7074 and SOLR-7233 where we discuss moving
zkcli.sh to bin and renaming it as {{bin/zk}}, and also let it have the ability
to start standalone zookeeper.
I'm a bit back and forth to what I think is best here. It sounds nice to keep
all ZK related things in a new {{bin/zk}}, but then if that script is able to
{{bin/zk start}}, {{bin/zk stop}}, {{bin/zk status}} etc, then it feels odd to
mix in upconfig/downconfig since those are solr-specific and client type of
operations. So I'm leaning towards letting {{bin/solr}} take care of the
solr-specific Zk interaction, so the sequence of events, if we implement
SOLR-7074 will be:
{noformat}
bin/zk start # We could let it sniff ZK_HOST from solr.in.sh?
bin/solr start
bin/solr zk upconfig -d path/to/config -n myconf
bin/solr create -c mycoll -n myconf
{noformat}
> Add upconfig and downconfig commands to the bin/solr script and managed-only
> schema to configsets
> -------------------------------------------------------------------------------------------------
>
> Key: SOLR-8378
> URL: https://issues.apache.org/jira/browse/SOLR-8378
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools
> Affects Versions: 5.4, Trunk
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Minor
> Attachments: SOLR-8378.patch, SOLR-8378.patch, SOLR-8378.patch,
> SOLR-8378.patch, SOLR-8378.patch
>
>
> It would be convenient to be able to upload and download arbitrary configsets
> to Zookeeper.
> This _might_ be the last thing we need before not requiring users be aware of
> zkcli, which is awkward.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]