You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Cassandra Targett (Jira)" <ji...@apache.org> on 2021/08/13 21:15:00 UTC

[jira] [Resolved] (SOLR-12050) UTILIZENODE does not enforce policy rules

     [ https://issues.apache.org/jira/browse/SOLR-12050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cassandra Targett resolved SOLR-12050.
--------------------------------------
    Resolution: Won't Fix

UTILIZENODE was removed as part of the removal of the autoscaling framework.

> UTILIZENODE does not enforce policy rules
> -----------------------------------------
>
>                 Key: SOLR-12050
>                 URL: https://issues.apache.org/jira/browse/SOLR-12050
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Chris M. Hostetter
>            Assignee: Noble Paul
>            Priority: Major
>         Attachments: SOLR-12050.log.txt
>
>
> I've been poking around TestUtilizeNode and some of it's recent jenkins failures -- AFAICT the {{UTILIZENODE}} is not behaving correctly per it's current documentation...
> bq. It tries to fix any policy violations first and then it tries to move some load off of the most loaded nodes according to the preferences
> ...based on my testing w/a slightly modified testcase that does additional logging/asserts, it will frequently choose to move a "random" replica to move, even when there are existing replicas that violate the policy.
> I will be commiting my current improvements to the test while citing this issue, and marking the test \@AwaitsFix  Then i'll attach some logs/comments showing what i mean.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org