[
https://issues.apache.org/jira/browse/SOLR-11201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376967#comment-16376967
]
Shalin Shekhar Mangar commented on SOLR-11201:
----------------------------------------------
This patch fixes the faulty assumption in the previous test. The earlier test
tried to assert that a particular operation is computed even though there are
no violations simulated by the test. This patch fixes by adding a new policy
after creating the collection such that there are explicit violations that
should be fixed.
> 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
> Priority: Major
> Fix For: master (8.0), 7.3
>
> Attachments: SOLR-11201-test-fix.patch, 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
