You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mikhail Khludnev (JIRA)" <ji...@apache.org> on 2019/02/21 06:00: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=16773687#comment-16773687 ]
Mikhail Khludnev commented on SOLR-12208:
-----------------------------------------
Hello, I suppose it's not hard to tackle
{quote}
Build: https://builds.apache.org/job/Lucene-Solr-Tests-master/3182/
1 tests failed.
FAILED: org.apache.solr.cloud.autoscaling.sim.TestSimExtremeIndexing.testScaleUp
Error Message:
java.util.concurrent.ExecutionException: java.util.ConcurrentModificationException
Stack Trace:
java.io.IOException: java.util.concurrent.ExecutionException: java.util.ConcurrentModificationException
at __randomizedtesting.SeedInfo.seed([EAB60F4AA87A3212:CBE849E8A454ECB3]:0)
at org.apache.solr.cloud.autoscaling.sim.SimCloudManager.request(SimCloudManager.java:656)
at org.apache.solr.cloud.autoscaling.sim.SimCloudManager$1.request(SimCloudManager.java:224)
at org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:207)
{quote}
> 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: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
> Fix For: 7.5, 8.0
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org