On 11/14/2019 12:28 AM, Werner Detter wrote:
I've got a SolrCloud instance with two collections running (Solr 7.7.2) on
Debian Stretch VMs. Every morning round about 03:3* am the collection gets
reset by $something and I have no clue what causes this and how to prevent
it as there areeven no log entries in SolrCloud (even with increased log level)
There is only one thing I know of that can delete data from an index
without an external trigger. It is the document expiration feature.
https://lucidworks.com/post/document-expiration/
Without some kind of action or intentional config, Solr will never
delete anything automatically. Solr does NOT contain any kind of
scheduling capability, and it might never get that functionality,
because ALL modern operating systems have something built in which can
schedule operations.
What precisely do you mean by "reset" in the above? Is the collection
still there but empty, or is the collection gone?
Can you grab and share the entire solr.log shortly after this happens,
and the previous logfile as well, which will most likely be named
solr.log.1?
Thanks,
Shawn
