On Wed, Mar 25, 2015 at 2:40 PM, Shawn Heisey <apa...@elyograg.org> wrote: > I think you will only need to change the ownership of the solr home and > the location where the .war file is extracted, which by default is > server/solr-webapp. The user must be able to *read* the program data, > but should not need to write to it. If you are using the start script > included with Solr 5 and one of the examples, I believe the logging > destination will also be located under the solr home, but you should > make sure that's the case.
Thanks Shawn, this sort of makes sense. The thing which I cannot seem to do is change the location where the war file is extracted. I think this is probably because, as of solr 5, I am not supposed to know or be aware that there is a war file, or that the war file is hosted in jetty, which makes it tricky to specify the jetty temporary directory. Our use case is that we want to create a single system image that would be usable for several projects, each project would check out its solr home and run solr as their own user (possibly on the same server). Eg, /data/projectA being a solr home for one project, /data/projectB being a solr home for another project, both running solr from the same location. Also, on a dev server, I want to install solr once, and each member of my team run it from that single location. Because they cannot change the temporary directory, and they cannot all own server/solr-webapp, this does not work and they must each have their own copy of the solr install. I think the way we will go for this is in production to run all our solr instance as the "solr" user, who will own the files in /opt/solr, and have their solr home directory wherever they choose. In dev, we will just do something... Cheers Tom
