As Susheel says, this is iffy, very iffy. You can disable tlogs entirely through solrconfig.xml, you can _probably_ disable all of the Solr logging.
You'd also have to _not_ run in SolrCloud. You say "some of the nodes eventually are stuck in the recovering phase" SolrCloud tries very hard to keep all of the replicas in sync. To do this it _must_ be able to copy from the leader to the follower. If it ever has to sync with the leader, it'll be stuck in recovery as you can see. You could spend a lot of time trying to make this work, but you haven't stated _why_ you want to. Perhaps there are other ways to get the functionality you want. Best, Erick On Fri, Jun 2, 2017 at 5:05 AM, Susheel Kumar <susheel2...@gmail.com> wrote: > I doubt it can run in readonly file system. Even though there is no > ingestion etc. Solr still needs to write to logs/tlogs for synching / > recovering etc.... > > Thnx > > On Fri, Jun 2, 2017 at 6:56 AM, Wudong Liu <wudong....@gmail.com> wrote: > >> Hi All: >> >> We have a normal build/stage -> prod settings for our production pipeline. >> And we would build solr index in the build environment and then the index >> is copied to the prod environment. >> >> The solrcloud in prod seems working fine when the file system backing it is >> writable. However, we see many errors when the file system is readonly. >> Many exceptions are thrown regarding the tlog file cannot be open for write >> when the solr nodes are restarted with the new data; some of the nodes >> eventually are stuck in the recovering phase and never able to go back >> online in the cloud. >> >> Just wondering is anyone has any experience on Solrcloud running in >> readonly file system? Is it possible at all? >> >> Regards, >> Wudong >>
