narendly opened a new pull request #938: Merge ZooScalability branch into master URL: https://github.com/apache/helix/pull/938 ### Description - [x] Here are some details about my PR, including screenshots of any UI changes: This PR rebases Zooscalability onto master and creates a PR for merging it into the master branch in upstream. ### Tests - [x] The following is the result of the "mvn test" command on the appropriate module: **helix-rest:** > [INFO] Results: > [INFO] > [ERROR] Failures: > [ERROR] TestResourceAccessor.testResourceHealth:289 expected:<HEALTHY> but was:<UNHEALTHY> > [INFO] > [ERROR] Tests run: 155, Failures: 1, Errors: 0, Skipped: 7 > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 40.763 s > [INFO] Finished at: 2020-04-08T15:57:26-07:00 > [INFO] ------------------------------------------------------------------------ TestResourceAccessor is a known failure that is being investigated separately. **metadata-store-directory-common:** > [INFO] Tests run: 30, Failures: 0, Errors: 0, Skipped: 0 > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 3.850 s > [INFO] Finished at: 2020-04-08T15:58:23-07:00 > [INFO] ------------------------------------------------------------------------ **zookeeper-api:** > [INFO] Tests run: 20, Failures: 0, Errors: 0, Skipped: 0 > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 6.053 s > [INFO] Finished at: 2020-04-08T15:59:21-07:00 > [INFO] ------------------------------------------------------------------------ **helix-core:** <PENDING> ### Commits - [x] 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 - [x] 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
