xyuanlu opened a new pull request #1101: URL: https://github.com/apache/helix/pull/1101
### Issues - [X] My PR addresses the following Helix issues and references them in the PR description: ### 1100 - [ ] Here are some details about my PR, including screenshots of any UI changes: Having a metric for number of expired session in zk client side will help user debugging cases that has frequent session expiration. This PR adds a "ExpiredSessionCounter" metrics in ZkClientMonitor. ### Tests - [X] The following tests are written for this issue: TestRawZkClient.testSessionExpireCount - [X] The following is the result of the "mvn test" command on the appropriate module: ' [ERROR] Failures: [ERROR] TestControllerLeadershipChange.testMissingTopStateDurationMonitoring:262 expected:<true> but was:<false> [ERROR] TestStateTransitionTimeoutWithResource.testStateTransitionTimeOut:171 expected:<true> but was:<false> [ERROR] TestAutoRebalance.testAutoRebalance:177 expected:<true> but was:<false> [ERROR] TestRoutingTableProviderPeriodicRefresh.testPeriodicRefresh:192 expected:<4> but was:<3> [ERROR] TestRebalanceRunningTask.testFixedTargetTaskAndDisabledRebalanceAndNodeAdded:297 expected:<true> but was:<false> [ERROR] TestHelixTaskExecutor.testCreateHandlerException:515 [INFO] [ERROR] Tests run: 1149, Failures: 6, Errors: 0, Skipped: 1 [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.852 s - in org.apache.helix.integration.controller.TestControllerLeadershipChange [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.636 s - in org.apache.helix.integration.paticipant.TestStateTransitionTimeoutWithResource [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.754 s - in org.apache.helix.integration.rebalancer.TestAutoRebalance [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.073 s - in org.apache.helix.integration.spectator.TestRoutingTableProviderPeriodicRefresh ‘ ### 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" ### Documentation (Optional) - [X] In case of new functionality, my PR adds documentation in the following wiki page: ### 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
