You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Noble Paul (JIRA)" <ji...@apache.org> on 2018/06/11 12:52:00 UTC
[jira] [Commented] (SOLR-12208) Don't use "INDEX.sizeInBytes" as a
tag name in policy calculations
[ https://issues.apache.org/jira/browse/SOLR-12208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16507981#comment-16507981 ]
Noble Paul commented on SOLR-12208:
-----------------------------------
[~ab] please take a look
> Don't use "INDEX.sizeInBytes" as a tag name in policy calculations
> ------------------------------------------------------------------
>
> Key: SOLR-12208
> URL: https://issues.apache.org/jira/browse/SOLR-12208
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling
> Reporter: Andrzej Bialecki
> Assignee: Noble Paul
> Priority: Major
> Attachments: SOLR-12208.patch
>
>
> CORE_IDX and FREEDISK ConditionType reuse this metric name, but they assume the values are expressed in gigabytes. This alone is confusing considering the name of the metric.
> Additionally, it causes conflicts in the simulation framework that would require substantial changes to resolve (ReplicaInfo-s in SimClusterStateProvider keep metric values in their variables, expressed in original units - but then the Policy assumes it can put the values expressed in GB under the same key... hilarity ensues).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org