[
https://issues.apache.org/jira/browse/SOLR-12050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382922#comment-16382922
]
ASF subversion and git services commented on SOLR-12050:
--------------------------------------------------------
Commit e2b3a97587a4387ab138252354d819ce253b625f in lucene-solr's branch
refs/heads/branch_7x from Chris Hostetter
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=e2b3a97 ]
SOLR-12050: mark TestUtilizeNode as AwaitsFix as well as adding additional
logging/assertions to help see what the bug is
(cherry picked from commit 0424d9c06ba52037024ce5f0f678b2aca8c34fb7)
> UTILIZENODE does not enforce policy rules
> -----------------------------------------
>
> Key: SOLR-12050
> URL: https://issues.apache.org/jira/browse/SOLR-12050
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
> Priority: Major
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
