lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <>
Subject [jira] [Commented] (SOLR-11833) Allow searchRate trigger to delete replicas
Date Thu, 19 Apr 2018 13:38:00 GMT


Shalin Shekhar Mangar commented on SOLR-11833:

bq. PULL replicas are not searchable, if I understand it correctly, so it doesn't make sense
to include them in search rate monitoring.

They participate in searches. They don't index data but periodically pull the latest segments
from the leader.

bq.  Rather, we could support rate but set aboveRate to this value and belowRate to 0 - this
will reproduce the behavior from 7.2 where there was no belowOp.


> Allow searchRate trigger to delete replicas
> -------------------------------------------
>                 Key: SOLR-11833
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: AutoScaling
>            Reporter: Andrzej Bialecki 
>            Assignee: Andrzej Bialecki 
>            Priority: Major
>             Fix For: 7.4, master (8.0)
>         Attachments: SOLR-11833.patch, SOLR-11833.patch
> Currently {{SearchRateTrigger}} generates events when search rate thresholds are exceeded,
and {{ComputePlanAction}} computes ADDREPLICA actions in response - adding replicas should
allow the search rate to be reduced across the increased number of replicas.
> However, once the peak load period is over the collection is left with too many replicas,
which unnecessarily tie cluster resources. {{SearchRateTrigger}} should detect situations
like this and generate events that should cause some of these replicas to be deleted.
> {{SearchRateTrigger}} should use hysteresis to avoid thrashing when the rate is close
to the threshold.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message