[jira] [Comment Edited] (SOLR-11492) More Modern cloud dev script
[ https://issues.apache.org/jira/browse/SOLR-11492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969610#comment-16969610 ] Robert Bunch edited comment on SOLR-11492 at 11/7/19 10:43 PM: --- Now that 8.3 is out, please give my 9/21 version of cloud.sh a shot. As I recall I did a lot of cleanup and whatnot, and the override file. Hmm... though this ticket is closed, guess I should just open a ticket and submit the patch? was (Author: bunchr): Now that 8.3 is out, please give my 9/21 version of cloud.sh a shot. As I recall I did a lot of cleanup and whatnot, and the override file. > 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 > Fix For: 8.3 > > Attachments: SOLR-11492.patch, cloud.sh, 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.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-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&focusedCommentId=16969610#comment-16969610 ] Robert Bunch commented on SOLR-11492: - Now that 8.3 is out, please give my 9/21 version of cloud.sh a shot. As I recall I did a lot of cleanup and whatnot, and the override file. > 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 > Fix For: 8.3 > > Attachments: SOLR-11492.patch, cloud.sh, 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.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-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&focusedCommentId=16960389#comment-16960389 ] Robert Bunch commented on SOLR-11492: - figured out what was going on w/ my fgc.sh script. ref the updated one in commentary in SOLR-13394. that's a variant of what I use to monitor the kajillion nodes I'm responsible for. > 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: SOLR-11492.patch, cloud.sh, 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.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-13394) Change default GC from CMS to G1
[ https://issues.apache.org/jira/browse/SOLR-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16960388#comment-16960388 ] Robert Bunch commented on SOLR-13394: - side note: I agree that all the JVM settings should be clearly documented as to WHY they're in there, what they do, why they some should be left alone, some optional... $0.02 > Change default GC from CMS to G1 > > > Key: SOLR-13394 > URL: https://issues.apache.org/jira/browse/SOLR-13394 > Project: Solr > Issue Type: Improvement >Reporter: Ishan Chattopadhyaya >Assignee: Ishan Chattopadhyaya >Priority: Major > Fix For: 8.1 > > Attachments: SOLR-13394.patch, SOLR-13394.patch > > Time Spent: 1h > Remaining Estimate: 0h > > CMS has been deprecated in new versions of Java > (http://openjdk.java.net/jeps/291). This issue is to switch Solr default from > CMS to G1. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-13394) Change default GC from CMS to G1
[
https://issues.apache.org/jira/browse/SOLR-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16960387#comment-16960387
]
Robert Bunch edited comment on SOLR-13394 at 10/26/19 4:17 PM:
---
late chiming in on this... but I agree, it'd be very, very helpful for it to
be a knob that can be turned (like -debug). Perhaps also enable JMX w/ the
same switch?
I manage a lot of clusters, Solr and ES, and any means of gathering info –
specifically old gen FGC's – is invaluable. Discovering the JVMs in the first
place is critical.
{code:java}
#!/bin/bash
for pid in `pgrep -f start.jar`; do
# for pid in `pgrep java`; do # normally I use this, as I don't have a local
ZK...
st=`ps -eo pid,etime | grep ${pid} | awk '{$1=""; print $0}'`
cli=`${JAVA_HOME}/bin/jinfo $pid 2>/dev/null | grep -i xmx | awk '{print
$3}'` # placement of -Xmx will vary
if [[ "`uname`" == "Darwin" ]]; then
port=`lsof -p $pid | grep TCP | grep LISTEN | grep :89 | awk '{print $9}'`
else
port=`netstat -nap 2>/dev/null | grep $pid | grep :89 | grep LISTEN | awk
'{print $4}'` # this will vary, JMX port conflict?
fi
echo $port | grep ":89" >/dev/null; is_solr_port=$?
if [[ $is_solr_port -eq 0 ]]; then
fgc=`${JAVA_HOME}/bin/jstat -gcutil $pid | awk '{print $9, $10}' | tail
-1` # this will vary, java 7 vs 8 vs... get count, time
if [[ "$cli" == "" ]]; then cli="UNKNOWN"; fi
printf "%s %6d %'9d %'11.2f %s %s\n" $port $pid $fgc $cli $st
fi
done | sort | egrep --color=always '^.*?[0-9]{4} +[0-9]{3,} +[0-9,]{4,} .*|$' #
change throttle of redline at 3rd grouping
for j in $(seq 1 60); do echo -n '.'; sleep 60; done{code}
when it works (port, pid, # old gen FGCs, total old gen FGC time, -Xmx param,
process uptime (days-hours:min:sec)
{code:java}
$ ./fgc-jira.sh
*:8981 15685 0 0.00 -Xmx1g 06:15:13
*:8982 15779 0 0.00 -Xmx1g 06:15:09
*:8983 15873 0 0.00 -Xmx1g 06:15:04
*:8984 15967 0 0.00 -Xmx1g 06:15:00
...^C (it'll tick off a dot for each minute, then an hour later here's another
sample){code}
when I can't get to that info (in this case, :8985 is 8.2 running vanilla w/
-XX:+PerfDisableSharedMem)
{code:java}
$ ./fgc-jira.sh
sun.jvmstat.monitor.MonitorException: 17297 not found
at
jdk.internal.jvmstat/sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.(PerfDataBuffer.java:84)
at
jdk.internal.jvmstat/sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.(LocalMonitoredVm.java:68)
at
jdk.internal.jvmstat/sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77)
at jdk.jcmd/sun.tools.jstat.Jstat.logSamples(Jstat.java:107)
at jdk.jcmd/sun.tools.jstat.Jstat.main(Jstat.java:70)
Caused by: java.lang.IllegalArgumentException: Could not map vmid to user Name
at java.base/jdk.internal.perf.Perf.attach(Native Method)
at java.base/jdk.internal.perf.Perf.attachImpl(Perf.java:270)
at java.base/jdk.internal.perf.Perf.attach(Perf.java:200)
at
jdk.internal.jvmstat/sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.(PerfDataBuffer.java:64)
... 4 more
./fgc-jira.sh: line 15: printf: -XX:+UseG1GC: invalid number
./fgc-jira.sh: line 15: printf: 58:12: invalid number
*:8981 15685 0 0.00 -Xmx1g 06:15:13
*:8982 15779 0 0.00 -Xmx1g 06:15:09
*:8983 15873 0 0.00 -Xmx1g 06:15:04
*:8984 15967 0 0.00 -Xmx1g 06:15:00
*:8985 17297 0 0.00 (blew up trying to get jinfo for this node)
...^C{code}
was (Author: bunchr):
late chiming in on this... but I agree, it'd be very, very helpful for it to
be a knob that can be turned (like -debug). Perhaps also enable JMX w/ the
same switch?
I manage a lot of clusters, Solr and ES, and any means of gathering info –
specifically old gen FGC's – is invaluable. Discovering the JVMs in the first
place is critical.
{code:java}
#!/bin/bash
for pid in `pgrep -f start.jar`; do
# for pid in `pgrep java`; do # normally I use this, as I don't have a local
ZK...
st=`ps -eo pid,etime | grep ${pid} | awk '{$1=""; print $0}'`
cli=`${JAVA_HOME}/bin/jinfo $pid 2>/dev/null | grep -i xmx | awk '{print
$3}'` # placement of -Xmx will vary
if [[ "`uname`" == "Darwin" ]]; then
port=`lsof -p $pid | grep TCP | grep LISTEN | grep :89 | awk '{print $9}'`
else
port=`netstat -nap 2>/dev/null | grep $pid | grep :89 | grep LISTEN | awk
'{print $4}'` # this will vary, JMX port conflict?
fi
echo $port | grep ":89" >/dev/null; is_solr_port=$?
if [[ $is_solr_port -eq 0 ]]; then
fgc=`${JAVA_HOME}/bin/jstat -gcutil $pid | awk '{print $9, $10}' | tail
-1` # this will vary, java 7 vs 8 vs... get count, time
if [[ "$cli" == "" ]]; then cli="UNKNOWN
[jira] [Commented] (SOLR-13394) Change default GC from CMS to G1
[
https://issues.apache.org/jira/browse/SOLR-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16960387#comment-16960387
]
Robert Bunch commented on SOLR-13394:
-
late chiming in on this... but I agree, it'd be very, very helpful for it to
be a knob that can be turned (like -debug). Perhaps also enable JMX w/ the
same switch?
I manage a lot of clusters, Solr and ES, and any means of gathering info –
specifically old gen FGC's – is invaluable. Discovering the JVMs in the first
place is critical.
{code:java}
#!/bin/bash
for pid in `pgrep -f start.jar`; do
# for pid in `pgrep java`; do # normally I use this, as I don't have a local
ZK...
st=`ps -eo pid,etime | grep ${pid} | awk '{$1=""; print $0}'`
cli=`${JAVA_HOME}/bin/jinfo $pid 2>/dev/null | grep -i xmx | awk '{print
$3}'` # placement of -Xmx will vary
if [[ "`uname`" == "Darwin" ]]; then
port=`lsof -p $pid | grep TCP | grep LISTEN | grep :89 | awk '{print $9}'`
else
port=`netstat -nap 2>/dev/null | grep $pid | grep :89 | grep LISTEN | awk
'{print $4}'` # this will vary, JMX port conflict?
fi
echo $port | grep ":89" >/dev/null; is_solr_port=$?
if [[ $is_solr_port -eq 0 ]]; then
fgc=`${JAVA_HOME}/bin/jstat -gcutil $pid | awk '{print $9, $10}' | tail
-1` # this will vary, java 7 vs 8 vs... get count, time
if [[ "$cli" == "" ]]; then cli="UNKNOWN"; fi
printf "%s %6d %'9d %'11.2f %s %s\n" $port $pid $fgc $cli $st
fi
done | sort | egrep --color=always '^.*?[0-9]{4} +[0-9]{3,} +[0-9,]{4,} .*|$' #
change throttle of redline at 3rd grouping
for j in $(seq 1 60); do echo -n '.'; sleep 60; done{code}
when it works (port, pid, # old gen FGCs, total old gen FGC time, -Xmx param,
process uptime (days-hours:min:sec)
{code:java}
$ ./fgc-jira.sh
*:8981 15685 0 0.00 -Xmx1g 06:15:13
*:8982 15779 0 0.00 -Xmx1g 06:15:09
*:8983 15873 0 0.00 -Xmx1g 06:15:04
*:8984 15967 0 0.00 -Xmx1g 06:15:00
...^C (it'll tick off a dot for each minute, then an hour later here's another
sample){code}
when I can't get to that info (in this case, :8985 is 8.2 running vanilla w/
-XX:+PerfDisableSharedMem)
{code:java}
$ ./fgc-jira.sh
sun.jvmstat.monitor.MonitorException: 17297 not found
at
jdk.internal.jvmstat/sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.(PerfDataBuffer.java:84)
at
jdk.internal.jvmstat/sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.(LocalMonitoredVm.java:68)
at
jdk.internal.jvmstat/sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77)
at jdk.jcmd/sun.tools.jstat.Jstat.logSamples(Jstat.java:107)
at jdk.jcmd/sun.tools.jstat.Jstat.main(Jstat.java:70)
Caused by: java.lang.IllegalArgumentException: Could not map vmid to user Name
at java.base/jdk.internal.perf.Perf.attach(Native Method)
at java.base/jdk.internal.perf.Perf.attachImpl(Perf.java:270)
at java.base/jdk.internal.perf.Perf.attach(Perf.java:200)
at
jdk.internal.jvmstat/sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.(PerfDataBuffer.java:64)
... 4 more
./fgc-jira.sh: line 15: printf: -XX:+UseG1GC: invalid number
./fgc-jira.sh: line 15: printf: 58:12: invalid number
$ ./fgc-jira.sh
*:8981 15685 0 0.00 -Xmx1g 06:15:13
*:8982 15779 0 0.00 -Xmx1g 06:15:09
*:8983 15873 0 0.00 -Xmx1g 06:15:04
*:8984 15967 0 0.00 -Xmx1g 06:15:00
*:8985 17297 0 0.00 (blew up trying to get jinfo for this node)
...^C{code}
> Change default GC from CMS to G1
>
>
> Key: SOLR-13394
> URL: https://issues.apache.org/jira/browse/SOLR-13394
> Project: Solr
> Issue Type: Improvement
>Reporter: Ishan Chattopadhyaya
>Assignee: Ishan Chattopadhyaya
>Priority: Major
> Fix For: 8.1
>
> Attachments: SOLR-13394.patch, SOLR-13394.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> CMS has been deprecated in new versions of Java
> (http://openjdk.java.net/jeps/291). This issue is to switch Solr default from
> CMS to G1.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-11492) More Modern cloud dev script
[ https://issues.apache.org/jira/browse/SOLR-11492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935022#comment-16935022 ] Robert Bunch edited comment on SOLR-11492 at 9/21/19 12:11 PM: --- no worries, and I agree. I made a commitment to clean it up some, specifically the ZK stack trace when chroot isn't there, but that can all be applied as a patch later. just didn't want you to think I ghosted you, since it's been several days and no other way to reach out... having said that, please give my new one a shot ;) – feedback welcome. I focused on cleaning up the start output when it's starting from newly built code. was (Author: bunchr): no worries, and I agree. I made a commitment to clean it up some, specifically the ZK stack trace when chroot isn't there, but that can all be applied as a patch later. just didn't want you to think I ghosted you, since it's been several days and no other way to reach out... > 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: SOLR-11492.patch, cloud.sh, 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.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-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&focusedCommentId=16935022#comment-16935022 ] Robert Bunch commented on SOLR-11492: - no worries, and I agree. I made a commitment to clean it up some, specifically the ZK stack trace when chroot isn't there, but that can all be applied as a patch later. just didn't want you to think I ghosted you, since it's been several days and no other way to reach out... > 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: SOLR-11492.patch, cloud.sh, 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.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-11492) More Modern cloud dev script
[ https://issues.apache.org/jira/browse/SOLR-11492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934895#comment-16934895 ] Robert Bunch edited comment on SOLR-11492 at 9/21/19 3:28 AM: -- finally got a chance to get back to this. cleaned it up, replaced "cloud-scripts/zkcli.sh" in favor of "bin/solr zk". introduced notion of an overrides file so devs don't have to hack the script for their stuff or constantly have to provide custom options all day long. :) (just put variables in cloud.sh.overrides, same location) uploaded new version. given cloud.sh isn't in cloud-dev yet, please advise if I should send content differently, vs. uploading the whole file. was (Author: bunchr): finally got a chance to get back to this. cleaned it up, replaced "cloud-scripts/zkcli.sh" in favor of "bin/solr zk". introduced notion of an overrides file so devs don't have to hack the script for their stuff or constantly have to provide custom options all day long. :) (just put variables in cloud.sh.overrides, same location) uploaded new version. > 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: SOLR-11492.patch, cloud.sh, 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.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-11492) More Modern cloud dev script
[ https://issues.apache.org/jira/browse/SOLR-11492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934895#comment-16934895 ] Robert Bunch edited comment on SOLR-11492 at 9/21/19 3:23 AM: -- finally got a chance to get back to this. cleaned it up, replaced "cloud-scripts/zkcli.sh" in favor of "bin/solr zk". introduced notion of an overrides file so devs don't have to hack the script for their stuff or constantly have to provide custom options all day long. :) (just put variables in cloud.sh.overrides, same location) uploaded new version. was (Author: bunchr): finally got a chance to get back to this. cleaned it up, replaced "cloud-scripts/zkcli.sh" in favor of "solr zk". introduced notion of an overrides file so devs don't have to hack the script for their stuff or constantly have to provide custom options all day long. :) (just put variables in cloud.sh.overrides, same location) uploaded new version. > 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: SOLR-11492.patch, cloud.sh, 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.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-11492) More Modern cloud dev script
[ https://issues.apache.org/jira/browse/SOLR-11492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934895#comment-16934895 ] Robert Bunch edited comment on SOLR-11492 at 9/21/19 3:20 AM: -- finally got a chance to get back to this. cleaned it up, replaced "cloud-scripts/zkcli.sh" in favor of "solr zk". introduced notion of an overrides file so devs don't have to hack the script for their stuff or constantly have to provide custom options all day long. :) (just put variables in cloud.sh.overrides, same location) uploaded new version. was (Author: bunchr): finally got a chance to get back to this. cleaned it up, replaced "cloud-scripts/zkcli.sh" in favor of "solr zk". introduced notion of an overrides file so devs don't have to hack the script for their stuff or constantly have to provide custom options all day long. :) (just put variables in cloud.sh.overrides, same location) will upload as cloud-rtb.sh to deconflict, 'till accepted. > 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: SOLR-11492.patch, cloud.sh, 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.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Updated] (SOLR-11492) More Modern cloud dev script
[ https://issues.apache.org/jira/browse/SOLR-11492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Bunch updated SOLR-11492: Attachment: cloud.sh > 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: SOLR-11492.patch, cloud.sh, 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.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-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&focusedCommentId=16934895#comment-16934895 ] Robert Bunch commented on SOLR-11492: - finally got a chance to get back to this. cleaned it up, replaced "cloud-scripts/zkcli.sh" in favor of "solr zk". introduced notion of an overrides file so devs don't have to hack the script for their stuff or constantly have to provide custom options all day long. :) (just put variables in cloud.sh.overrides, same location) will upload as cloud-rtb.sh to deconflict, 'till accepted. > 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: SOLR-11492.patch, cloud.sh, 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.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-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&focusedCommentId=16930161#comment-16930161 ] Robert Bunch commented on SOLR-11492: - there's a few other nuts 'n bolts I'd like to work in the script, at least cleaning up some of the "errors" that pop up when starting new... > 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: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-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&focusedCommentId=16930001#comment-16930001 ] Robert Bunch commented on SOLR-11492: - against Ubuntu 14.04.6/Trusty LTS * new -r [OK] * stop [OK] * start [OK] * the problem child ... restart -c ... [OK] COLLECTIONS FOUND IN ZK enron enron3 enron2 nuke enron Removing Zookeeper node /solr__home_bunchr_Downloads_lab_2019-09-15/collections/enron from ZooKeeper at localhost:2181 recurse: true 0 nuke enron3 Removing Zookeeper node /solr__home_bunchr_Downloads_lab_2019-09-15/collections/enron3 from ZooKeeper at localhost:2181 recurse: true 0 nuke enron2 Removing Zookeeper node /solr__home_bunchr_Downloads_lab_2019-09-15/collections/enron2 from ZooKeeper at localhost:2181 recurse: true 0 > 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: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-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&focusedCommentId=16929991#comment-16929991 ] Robert Bunch commented on SOLR-11492: - Yep, worked fine on Mac OS 10.14.6 (Mojave) and CentOS 6. I imagine it'd work fine on Ubuntu; I have an older LTS I can bang it against. Just needs to have a caveat that it should be a clean/dedicated working dir, or script tweaked to look for a particular pattern of dirs to pluck from. > 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: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
