[
https://issues.apache.org/jira/browse/SOLR-11201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296960#comment-16296960
]
Andrzej Bialecki commented on SOLR-11201:
------------------------------------------
I think that the configuration should also specify what is the preferred action
- in many cases this will be MOVEREPLICA, but if we plan to use this trigger
for other metrics then other actions may be more appropriate depending on the
metric (eg. ADDREPLICA, REPLACENODE, SPLITSHARD, etc).
> 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
>
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
