[
https://issues.apache.org/jira/browse/SOLR-11201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-11201:
-----------------------------------------
Attachment: SOLR-11201.patch
Thanks Andrzej. This patch adds a optional property named 'preferredOperation'
to the trigger that can be used to change the default operation (MOVEREPLICA).
However, on writing a test that sets preferredOperation to addreplica, I found
that the policy can return an unbounded number of suggestions. I believe a
similar bug was found in the search rate trigger. So for now, I have commented
out that test.
> Implement trigger for arbitrary metrics
> ---------------------------------------
>
> Key: SOLR-11201
> URL: https://issues.apache.org/jira/browse/SOLR-11201
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling, SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Fix For: 7.2
>
> Attachments: SOLR-11201.patch, SOLR-11201.patch
>
>
> It should be possible to set a trigger on any metrics exposed by the Metrics
> API using a threshold value. Supporting {{waitFor}} may not be possible or
> useful for all metrics. For those we will implement proper trigger support
> (such as searchRate) However, a naive implementation might be to just poll
> the value of the metric frequently and if it is consistently above the
> threshold, fire the trigger.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
