[
https://issues.apache.org/jira/browse/SOLR-11726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett resolved SOLR-11726.
--------------------------------------
Resolution: Done
Resolving as Done; some issues were completed but some closed as Won't Fix
after the autoscaling framework was removed.
> Analyze and verify dynamic behavior of the autoscaling framework
> ----------------------------------------------------------------
>
> Key: SOLR-11726
> URL: https://issues.apache.org/jira/browse/SOLR-11726
> Project: Solr
> Issue Type: Task
> Components: AutoScaling
> Reporter: Andrzej Bialecki
> Priority: Major
>
> Currently most unit and integration tests verify the static behavior of
> autoscaling, ie. they introduce a change and then wait until the state of the
> system stabilizes, and then make assertions.
> While this testing is necessary it doesn't address the issues related to
> transient responses of the framework to changes in time. It's also important
> to learn the timescale of the framework's reactions to such events, and its
> behavior when faced with overlapping / conflicting events.
> One simple example that illustrates the need for this kind of testing is a
> scenario with a flaky node that periodically comes down and up again.
> Depending on the frequency of changes and the trigger configuration (eg.
> {{waitFor}} value) the current implementation of the framework may lead at
> best to high churn (as replicas are being moved around) or even to data loss
> (by moving replicas to a flaky node).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
