[jira] [Commented] (SOLR-11492) More Modern cloud dev script
[
https://issues.apache.org/jira/browse/SOLR-11492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926853#comment-16926853
]
Robert Bunch commented on SOLR-11492:
-
script works on Mac OS (Mojave) and CentOS 6.
however, on Mac OS, w/ master branch build of Solr – using "-c" option to
harvest the collections results in repeatably *{color:#FF}rebooting{color}*
the Mac! (not running it as root...)
on CentOS 6, after the Solr JVMs have been restarted (and verified w/
CLUSTERSTATUS, LIST) – eventually OS threads are exhausted:
{code:java}
[bunchr@localhost lab]$ ls
bash: fork: retry: Resource temporarily unavailable
bash: fork: retry: Resource temporarily unavailable
bash: fork: retry: Resource temporarily unavailable
bash: fork: retry: Resource temporarily unavailable
:
:
:{code}
...and pretty much have to reboot (further investigations at the *nix level are
warranted) or nuke the JVMs to get the box back under control.
Workaround is to stop solr via script (or kill -9 `pgrep -f start.jar`), and do
a deleteall /solr.../collections/... (whatever needs to be cleaned up). inside
start() after SAFE_DEST is defined:
{code:java}
275 # RTB 2019-09-10
276 echo COLLECTIONS FOUND IN ZK | egrep --color=always '.*'
277 COLLECTIONS_TO_CLEAN=`${SOLR}/bin/solr zk ls
/solr_${SAFE_DEST}/collections -z localhost:2181`; echo
$COLLECTIONS_TO_CLEAN | egrep --color=always '.*'
278 if [[ "$CLEAN" == "true" ]]; then
279 for collection in ${COLLECTIONS_TO_CLEAN}; do
280 echo nuke $collection
281 ${SOLR}/bin/solr zk rm -r
/solr_${SAFE_DEST}/collections/${collection} -z localhost:2181
282 echo $?
283 done
284 fi
285 # end RTB 2019-09-10
{code}
> More Modern cloud dev script
>
>
> Key: SOLR-11492
> URL: https://issues.apache.org/jira/browse/SOLR-11492
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
>Affects Versions: 8.0
>Reporter: Gus Heck
>Assignee: Gus Heck
>Priority: Minor
> Attachments: cloud.sh, 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
(v8.3.2#803003)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11492) More Modern cloud dev script
[ https://issues.apache.org/jira/browse/SOLR-11492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926689#comment-16926689 ] Gus Heck commented on SOLR-11492: - current versions living here until I get some feedback and verification that works on machines other than mine :) [https://gist.github.com/nsoft/d05d9e3f019ac823c0fe418f1f4bee5d] > More Modern cloud dev script > > > Key: SOLR-11492 > URL: https://issues.apache.org/jira/browse/SOLR-11492 > Project: Solr > Issue Type: Improvement > Components: SolrCloud >Affects Versions: 8.0 >Reporter: Gus Heck >Assignee: Gus Heck >Priority: Minor > Attachments: cloud.sh, 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 (v8.3.2#803003) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11492) More Modern cloud dev script
[ https://issues.apache.org/jira/browse/SOLR-11492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674437#comment-16674437 ] Gus Heck commented on SOLR-11492: - updated: last version had an issue with an extra pushd command, and also didn't provide a good message for the case where the tarball doesn't exist. > 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, > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11492) More Modern cloud dev script
[
https://issues.apache.org/jira/browse/SOLR-11492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674304#comment-16674304
]
Gus Heck commented on SOLR-11492:
-
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 [options] [name]
Options:
-cclean the data directories erasing all indexed data
-rrecompile server with 'ant clean server create-package'
-n number of nodes to create/start if this doesn't match error
-w path to the vcs checkout (ignored unless -r)
-z port to look for zookeeper on (2181 default)
Commands:
new Create a new cluster and start it
startStart 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11492) More Modern cloud dev script
[ https://issues.apache.org/jira/browse/SOLR-11492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674285#comment-16674285 ] Gus Heck commented on SOLR-11492: - tweaks to make it work on osx and new now implies -r to ensure we fetch and unpack a tarball before trying to start > 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 > > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11492) More Modern cloud dev script
[ https://issues.apache.org/jira/browse/SOLR-11492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674263#comment-16674263 ] Gus Heck commented on SOLR-11492: - I completely rewrote this to be far more useful and have more standard option based interface. When I tried to move to a new repo for commit work I realized I had been relying on a bunch of commands before and after this script on the bash history line, and those lines tended to have directory names baked in that made it hard to easily do things like have a cluster for just testing one issue. If others think they would use the new version, I'll be happy to check it into either of /solr/cloud-dev or /dev-tools/scripts > 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 > > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11492) More Modern cloud dev script
[ https://issues.apache.org/jira/browse/SOLR-11492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16210273#comment-16210273 ] Gus Heck commented on SOLR-11492: - Ah good find... that seem to also work on ubuntu linux so I'll go with that > 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 >Priority: Minor > Attachments: 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 (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11492) More Modern cloud dev script
[
https://issues.apache.org/jira/browse/SOLR-11492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209688#comment-16209688
]
David Smiley commented on SOLR-11492:
-
This looks cool.
I wanted to try it but failed because on Mac OS X, a BSD derivative, the "date"
executable doesn't support {{date -I}} so I replaced it with {{date
"+%Y\-%m\-%d"}}
> 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
>Priority: Minor
> Attachments: 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
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
