[
https://issues.apache.org/jira/browse/SOLR-12483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511352#comment-16511352
]
Andrzej Bialecki commented on SOLR-12483:
------------------------------------------
To make it clear, this issue is about recommending (not executing) possible
optimizations to the cluster. This is different that what triggers do, which is
to detect and execute (control) actions to keep cluster parameters to fit
within configured bounds.
Trend detection is a complex topic in general so we probably should not work
any any sophisticated solutions in Solr for this - we have the metrics history
API (SOLR-11779) so that external tools can analyze this data and implement
their own rules and trend detection, and decide on possible optimizations (eg.
"add more replicas on Fridays").
Solr may provide only some basic trend detection, eg. linear regression for
detecting monotonic trends, and Fourier transform for detecting cyclic trends.
> Trend based suggestions
> -----------------------
>
> Key: SOLR-12483
> URL: https://issues.apache.org/jira/browse/SOLR-12483
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Priority: Major
>
> A cluster may be perfectly fine now and it may not be so in the future. It is
> possible to extrapolate past trends to predict the future state certain
> values. Solr can make recommendations to
> * Move replica
> * Add node
> based on these projections
> We can use SOLR-11779 to see the historic trend for various values such as
> {{freedisk}} , {{queries per second}} , {{index size}} etc . it is possible
> to extrapolate the future values and make recommendations
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
