[
https://issues.apache.org/jira/browse/SOLR-11200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16444900#comment-16444900
]
Hoss Man commented on SOLR-11200:
---------------------------------
we could potentially do that with an autoscalling trigger – but that doesn't
really negate the value of having an explicit setting for this.
If the settings is true/false then force the underlying CMS value to true/false
... down the road, if someone wants to try writting a trigger that monitors
disk IO and the search rate, that trigger could be designed to respect the
explicit setting if set (and be a NoopTrigger) – but if the setting is
unspecified, then dynmaically toggle the underlying value on the CMS directly
as the trigger condition happens.
> provide a config to enable disable ConcurrentMergeSchedule.doAutoIOThrottle
> ---------------------------------------------------------------------------
>
> Key: SOLR-11200
> URL: https://issues.apache.org/jira/browse/SOLR-11200
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Nawab Zada Asad iqbal
> Priority: Minor
> Attachments: SOLR-11200.patch, SOLR-11200.patch, SOLR-11200.patch
>
>
> This config can be useful while bulk indexing. Lucene introduced it
> https://issues.apache.org/jira/browse/LUCENE-6119 .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
