[
https://issues.apache.org/jira/browse/SOLR-11492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674304#comment-16674304
]
Gus Heck edited comment on SOLR-11492 at 11/4/18 5:40 AM:
----------------------------------------------------------
One more set of tweaks to make behavior more consistent, and allow deployment
of previously built tarball, plus examples in comment at top
Create a brand new 4 node cluster deployed in a directory named for today
{code:java}
./cloud.sh new{code}
Create a brand new 4 node cluster deployed in a directory named SOLR-1234567
{code:java}
./cloud.sh new SOLR-1234567{code}
Stop the cluster
{code:java}
./cloud.sh stop{code}
Compile and push new code to a running cluster (incl bounce the cluster)
{code:java}
./cloud.sh restart -r{code}
Dump your hoplessly fubar'd collections and start fresh with the existing
tarball
{code:java}
./cloud.sh restart -c{code}
Additional options...
{code:none}
Usage:
./cloud.sh <command> [options] [name]
Options:
-c clean the data directories erasing all indexed data
-r recompile server with 'ant clean server create-package'
-n <num> number of nodes to create/start if this doesn't match error
-w <path> path to the vcs checkout
-z <num> port to look for zookeeper on (2181 default)
Commands:
new Create a new cluster and start it
start Start an existing cluster specified by [name]
stop stop the cluster specified by [name]
restart stop and then start
{code}
was (Author: gus_heck):
One more set of tweaks to make behavior more consistent, and allow deployment
of previously built tarball, plus examples in comment at top
Create a brand new 4 node cluster deployed in a directory named for today
{code:java}
./cloud.sh new{code}
Create a brand new 4 node cluster deployed in a directory named SOLR-1234567
{code:java}
./cloud.sh new SOLR-1234567{code}
Stop the cluster
{code:java}
./cloud.sh stop{code}
Compile and push new code to a running cluster (incl bounce the cluster)
{code:java}
./cloud.sh restart -r{code}
Dump your hoplessly fubar'd collections and start fresh with the existing
tarball
{code:java}
./cloud.sh restart -c{code}
Additional options...
{code:none}
Usage:
./cloud.sh <command> [options] [name]
Options:
-c clean the data directories erasing all indexed data
-r recompile server with 'ant clean server create-package'
-n <num> number of nodes to create/start if this doesn't match error
-w <path> path to the vcs checkout (ignored unless -r)
-z <num> port to look for zookeeper on (2181 default)
Commands:
new Create a new cluster and start it
start Start an existing cluster specified by [name]
stop stop the cluster specified by [name]
restart stop and then start
{code}
> More Modern cloud dev script
> ----------------------------
>
> Key: SOLR-11492
> URL: https://issues.apache.org/jira/browse/SOLR-11492
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: master (8.0)
> Reporter: Gus Heck
> Assignee: Gus Heck
> Priority: Minor
> Attachments: cloud.sh, cloud.sh, cloud.sh, cloud.sh, cloud.sh
>
>
> Most of the scripts in solr/cloud-dev do things like start using java -jar
> and other similarly ancient techniques. I recently decided I really didn't
> like that it was a pain to setup a cloud to test a patch/feature and that
> often one winds up needing to blow away existing testing so working on more
> than one thing at a time is irritating... so here's a script I wrote, if
> folks like it I'd be happy for it to be included in solr/cloud-dev
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
