Just got back to this, thanks for your help Shawn. Agree that docker is the problem here, I don't have time/need for this experiment to faff with docker so I've gone back to monolithic solr installed in /opt. It's not going to be in production anyway. I'll move on to other problems. Be useful if someone finds this thread to post an answer to clear it up.
Tim On Tue, 21 Mar 2023 at 14:20, Shawn Heisey <apa...@elyograg.org> wrote: > On 3/20/23 14:42, Tim Clarke wrote: > > Sorry, I'd stopped it before answering you. I get this after starting: > > > > timc@Debian:$ docker exec 9a65798bda0d ps aux | grep solr > > Neither the "-e schemaless" nor "-Dsolr.modules=extraction" options were > honored in the actual solr startup inside the container. I checked > carefully in the output you shared. > > I ran this command after building the 9.3.0-SNAPSHOT docker image: > > docker run -p 8983:8983 -e SOLR_MODULES=extraction -e SOLR_HEAP=4g > apache/solr:9.3.0-SNAPSHOT > > And this was the relevant line from the "docker exec" command: > > solr 14 141 4.9 12732896 4528244 ? Sl 22:26 0:23 > /opt/java/openjdk/bin/java -server -Xms4g -Xmx4g -XX:+UseG1GC > -XX:+PerfDisableSharedMem -XX:+ParallelRefProcEnabled > -XX:MaxGCPauseMillis=250 -XX:+UseLargePages -XX:+AlwaysPreTouch > -XX:+ExplicitGCInvokesConcurrent > -Xlog:gc*:file=/var/solr/logs/solr_gc.log:time,uptime:filecount=9,filesize=20M > > -Dsolr.jetty.inetaccess.includes= -Dsolr.jetty.inetaccess.excludes= > -Dsolr.log.dir=/var/solr/logs -Djetty.port=8983 -DSTOP.PORT=7983 > -DSTOP.KEY=solrrocks -Duser.timezone=UTC -XX:-OmitStackTraceInFastThrow > -XX:+CrashOnOutOfMemoryError > -XX:ErrorFile=/var/solr/logs/jvm_crash_%p.log > -Djetty.home=/opt/solr-9.3.0-SNAPSHOT/server > -Dsolr.solr.home=/var/solr/data > -Dsolr.install.dir=/opt/solr-9.3.0-SNAPSHOT > -Dsolr.install.symDir=/opt/solr > -Dsolr.default.confdir=/opt/solr-9.3.0-SNAPSHOT/server/solr/configsets/_default/conf > > -Dlog4j.configurationFile=/var/solr/log4j2.xml -Dsolr.modules=extraction > -Dsolr.jetty.host=0.0.0.0 -Xss256k > -XX:CompileCommand=exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put > > -Djava.security.manager > -Djava.security.policy=/opt/solr-9.3.0-SNAPSHOT/server/etc/security.policy > -Djava.security.properties=/opt/solr-9.3.0-SNAPSHOT/server/etc/security.properties > > -Dsolr.internal.network.permission=* -DdisableAdminUI=false -jar > start.jar --module=http --module=requestlog --module=gzip > > You can see that the two environment variables I set did affect the > startup commandline. > > I think the problem with the docker run command that you used is that > the options you provided were handled by docker, and not sent as-is to > the Solr start script inside the container. > > Just in the last few days, I have encountered evidence that some of what > the ref guide shows for running the docker image is not actually > supported by the docker image. Maybe there are more things wrong. > > I don't know that there is actually a way to have the docker image > easily run an example. You wouldn't want to run an example in > production anyway. > > Something you can do is just use the config from the schemaless example > when you create a new collection. > > Thanks, > Shawn >
