[
https://issues.apache.org/jira/browse/SOLR-12208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509337#comment-16509337
]
ASF subversion and git services commented on SOLR-12208:
--------------------------------------------------------
Commit 6013fa4aeb2113746153cef25e0a8b8be3ae090a in lucene-solr's branch
refs/heads/branch_7x from [~noble.paul]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=6013fa4 ]
SOLR-12208: ignored the test , because it fails now
> 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
> Fix For: master (8.0), 7.5
>
> Attachments: SOLR-12208.patch, SOLR-12208.patch, 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: [email protected]
For additional commands, e-mail: [email protected]
