lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrzej Bialecki (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SOLR-12757) Don't load cores that belong to inactive shards
Date Mon, 10 Sep 2018 12:49:00 GMT
Andrzej Bialecki  created SOLR-12757:
----------------------------------------

             Summary: Don't load cores that belong to inactive shards
                 Key: SOLR-12757
                 URL: https://issues.apache.org/jira/browse/SOLR-12757
             Project: Solr
          Issue Type: Improvement
      Security Level: Public (Default Security Level. Issues are Public)
          Components: AutoScaling
            Reporter: Andrzej Bialecki 
            Assignee: Andrzej Bialecki 


After shard splitting completes and the new sub-shards become active the original (parent)
shards is switched to inactive state. Since 7.4 Solr runs a scheduled trigger that uses {{InactiveShardPlanAction}}
to eventually remove inactive shards when their TTL expires (2 days by default).

However, in the meantime even though the shard is inactive all cores that belong to this shard
are still running, and should a node restart these cores would be loaded again too.

Large scale simulated tests show that in case of a constantly growing index after a while
most of the cluster resources are consumed by cores that belong to inactive shards.

We should change this so that when the switch-over to the new sub-shards is complete the cores
belonging to the inactive parent shard should be unloaded and not loaded again - at the very
least it should be made into an option that is true by default.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message