zpinto opened a new pull request, #2743: URL: https://github.com/apache/helix/pull/2743
### Issues - [x] isEvacuationCompleted is returning false for instances with SEMI_AUTO resources assigned to it. ### Description Evacuation is not supported for SEMI_AUTO resources. It is the customers job to populate the preferenceList. Evacuate does not make since in this context because EVACUATION relies on rebalancer to decide a new destination for the replicas. If the resource is not FULL_AUTO, helix is not allowed to modify the preferenceList. We are fixing the API to only consider the CURRENTSTATE of FULL_AUTO resources in the check to see if evacuation has is finished. ### Tests - [x] testEvacuate is modified to create semi auto resource assigned to all participants and we call evacuate and isEvacuateFinished is successful ### Changes that Break Backward Compatibility (Optional) NA ### Documentation (Optional) NA ### Commits - My commits all reference appropriate Apache Helix GitHub issues in their subject lines. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)": 1. Subject is separated from body by a blank line 1. Subject is limited to 50 characters (not including Jira issue reference) 1. Subject does not end with a period 1. Subject uses the imperative mood ("add", not "adding") 1. Body wraps at 72 characters 1. Body explains "what" and "why", not "how" ### Code Quality - My diff has been formatted using helix-style.xml (helix-style-intellij.xml if IntelliJ IDE is used) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
