[ 
https://issues.apache.org/jira/browse/SOLR-12463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504967#comment-16504967
 ] 

Shalin Shekhar Mangar commented on SOLR-12463:
----------------------------------------------

You can change the trigger delay by setting an autoscaling property called 
"triggerScheduleDelaySeconds". However, it changes the delay for all triggers. 
We don't support different delays for different triggers today. Doing so seems 
complicated to me without much upside.

> Search rate trigger should check metrics less often
> ---------------------------------------------------
>
>                 Key: SOLR-12463
>                 URL: https://issues.apache.org/jira/browse/SOLR-12463
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: AutoScaling
>            Reporter: Varun Thacker
>            Priority: Major
>
> I created a search rate trigger by running this command 
> {code:java}
> curl -X POST -H 'Content-type:application/json' --data-binary '{
> "set-trigger": {
> "name" : "search_rate_trigger",
> "event" : "searchRate",
> "collection" : "gettingstarted",
> "rate" : 1.0,
> "waitFor" : "1m",
> "enabled" : true,
> "actions" : [
> {
> "name" : "compute_plan",
> "class": "solr.ComputePlanAction"
> },
> {
> "name" : "execute_plan",
> "class": "solr.ExecutePlanAction"
> }
> ]
> }
> }' http://localhost:8983/solr/admin/autoscaling
> {code}
> As soon as I add this by logs start getting spammed with these every 1 second
> {code:java}
> INFO  - 2018-06-07 15:29:16.243; [   ] org.apache.solr.servlet.HttpSolrCall; 
> [admin] webapp=null path=/admin/metrics 
> params={wt=javabin&version=2&key=solr.core.gettingstarted.shard2.replica_n4:QUERY./select.requestTimes:1minRate&key=solr.core.gettingstarted.shard1.replica_n1:QUERY./select.requestTimes:1minRate}
>  status=0 QTime=0
> INFO  - 2018-06-07 15:29:17.253; [   ] org.apache.solr.servlet.HttpSolrCall; 
> [admin] webapp=null path=/admin/metrics 
> params={wt=javabin&version=2&key=solr.core.gettingstarted.shard2.replica_n4:QUERY./select.requestTimes:1minRate&key=solr.core.gettingstarted.shard1.replica_n1:QUERY./select.requestTimes:1minRate}
>  status=0 QTime=0
> INFO  - 2018-06-07 15:29:18.263; [   ] org.apache.solr.servlet.HttpSolrCall; 
> [admin] webapp=null path=/admin/metrics 
> params={wt=javabin&version=2&key=solr.core.gettingstarted.shard2.replica_n4:QUERY./select.requestTimes:1minRate&key=solr.core.gettingstarted.shard1.replica_n1:QUERY./select.requestTimes:1minRate}
>  status=0 QTime=0
> ....{code}
> Does 1 second seem to aggressive ? 
> Maybe the waitFor could be taken into account and query the metrics at 
> waitFor/2 or something ? 



--
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

Reply via email to