Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
-
None
Description
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...
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.