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

Andrzej Bialecki  commented on SOLR-12181:
------------------------------------------

This patch adds {{IndexSizeTrigger}}, tests and supporting changes, among 
others:
* a barebones {{SplitShardSuggester}} to handle SPLITSHARD requests
* stubs to handle the future MERGESHARDS (SOLR-9407)
* extensions to the simulation framework to support index updates, tracking 
index size and document count metrics.

The trigger supports mixed lower and upper bounds defined in terms of index 
size (using the {{INDEX.sizeInBytes}} metric) and document counts (using the 
{{SEARCHER.searcher.numDocs}} metric), as well as defining custom operations to 
perform when bounds are exceeded, both lower and upper ones:

* aboveBytes - upper bound defined using index size in bytes
* aboveDocs - upper bound defined using number of docs
* belowBytes - lower bound defined using index size in bytes
* belowDocs - lower bound defined using number of docs
* aboveOp - operation to perform when any upper bound is exceeded. The default 
operation is SPLITSHARD
* belowOp - operation to perform when any lower bound is exceeded. The default 
operation is MERGESHARDS
* collections - comma-separated list of collections, or empty / none to 
consider all collections

> Add trigger based on document count
> -----------------------------------
>
>                 Key: SOLR-12181
>                 URL: https://issues.apache.org/jira/browse/SOLR-12181
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: AutoScaling
>    Affects Versions: master (8.0)
>            Reporter: Andrzej Bialecki 
>            Assignee: Andrzej Bialecki 
>            Priority: Major
>         Attachments: SOLR-12181.patch
>
>
> This may turn out to be as simple as using a {{MetricTrigger}} but it's 
> likely this will require some specialization, and we may want to add this 
> type of trigger anyway for convenience.
> The two control actions associated with this trigger will be SPLITSHARD and 
> (yet nonexistent) MERGESHARD.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to