I feel that maybe we don't treat it special mentally, but then it actually is. At least with minimum custom locations configured.
Consider: 1) What is in "server", above "server/solr" * resources/log4j2.xml (because of magic jetty classpath mechanism) * logs * NOT server/solr/configsets (but probably should be to avoid confusion with recursive core searching algorithm or just people trying to understand what those directories are) 2) What is in "example/schemaless" * logs (because of hardcoded magic in bin/solr) * NOT log4j2.xml, because we simplified it but also lost an ability to customize 3) What is in "example/cloud/node1" * logs (same magic) >From other discussions, if you try to reproduce examples outside of the example directory, they will log to the global log directory and mess with each other, unless you pass on an individual log directory location for each bin/solr command. I am wondering if the example above solr.home should be the place we try to check for: 1) logging configuration (or override that latest log4 seems to support) 2) logs 3) configsets available to that node 4) maybe solr.in.sh This would certainly make example setups easy and less magical. I don't know if this is the right answer. I specifically don't know if this will mess up cloud setups. But I see a pattern that is unacknowledged and think that maybe acknowledging would allow us to have a more general solution that magic in bin/solr. And maybe just in time for the Solr in Docker final decisions. Regards, Alex. P.s. To make it more interesting, I am also confused about pid files going into bin directory. I bet docker image puts them somewhere else. On Fri, 4 Sep 2020 at 01:04, David Smiley <dsmi...@apache.org> wrote: > > The parent directory of Solr home is not special. Where Solr Home is (as you > know) configurable. It's default location is different too, since it's in > /var/solr for both the Docker & service install script. > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > > On Tue, Aug 25, 2020 at 8:31 PM Alexandre Rafalovitch <arafa...@gmail.com> > wrote: >> >> Hello, >> >> What do we call the directory above the solr.home? >> E.g. >> - "schemaless" in example/schemaless/solr/gettingstarted >> - "node1" in example/cloud/node1/solr/gettingstarted_shard1_replica_n2 >> - "solr" in server/solr/book/conf >> >> In solr.in.cmd we "may be" calling it "solr start dir" >> In bin/solr, we call it SOLR_SERVER_DIR >> In install_solr-service.sh, we sort-of call it SOLR_VAR_DIR "Directory >> for live/writable Solr files", which is not quite the same because >> apparently pid files go there, while for distribution they seem to go >> into bin >> >> I guess it mostly matters when you have multiple Solr instances >> running on the same machine and you need to separate log locations, >> etc. >> >> Regards, >> Alex. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
