On 11/14/2019 9:17 AM, Werner Detter wrote:
first, thanks for your response. By "reset" I mean: collection still exists but documents have been dropped (from actually round 50k to 0). It happened twice within the same timeframe early in the morning the last two days so I was wondering if something within Solr like this:".scheduled_maintenance":{ "name":".scheduled_maintenance", "event":"scheduled", "startTime":"NOW", "every":"+1DAY", "enabled":true, "actions" { "name":"inactive_shard_plan", "class":"solr.InactiveShardPlanAction"}, { "name":"inactive_markers_plan", "class":"solr.InactiveMarkersPlanAction"}, { "name":"execute_plan", "class":"solr.ExecutePlanAction"}]}}, could be the reason for the resets due to $something =) But I'm not sure about those Solr maintenance things, that's why I initially asked on the mailinglist here. But you said Solr doesn't contain any internal scheduling capability which means this is probably something else. There are no crons on the operating system itself that do any kind of solr maintenance.
I was unaware of that config. Had to look it up. I have never looked at the autoscaling feature. I'm not even sure what that config will actually do. To me, it doesn't look like it's configured to do much.
Someone who is familiar with that feature will need to chime in and confirm/refute my thoughts, but as far as I know, it is only capable of things like adding or removing replicas, not deleting the data or the index.
Seeing the logs, with them set to the defaults that Solr ships, might reveal something.
Thanks, Shawn
