[
https://issues.apache.org/jira/browse/HELIX-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778873#comment-16778873
]
Hudson commented on HELIX-812:
------------------------------
FAILURE: Integrated in Jenkins build helix #1607 (See
[https://builds.apache.org/job/helix/1607/])
[HELIX-812] HELIX: Fix maintenance history bug (narendly: rev
4ecd923f279a53554fc66e9a71356af2f125c451)
* (edit)
helix-core/src/test/java/org/apache/helix/integration/controller/TestClusterMaintenanceMode.java
* (edit)
helix-core/src/main/java/org/apache/helix/controller/dataproviders/BaseControllerDataProvider.java
* (edit)
helix-core/src/main/java/org/apache/helix/controller/stages/MaintenanceRecoveryStage.java
> HELIX: Fix maintenance history bug
> ----------------------------------
>
> Key: HELIX-812
> URL: https://issues.apache.org/jira/browse/HELIX-812
> Project: Apache Helix
> Issue Type: Improvement
> Reporter: Hunter L
> Assignee: Hunter L
> Priority: Major
>
> There was a bug in maintenance history where when the cluster exits
> maintenance mode automatically, it would record the exit action twice in
> history. This is because each pipeline is designed to run
> MaintenanceRecoveryStage twice.
> Changelist:
> 1. Add a flag so that if maintenanceSignal has been changed, just return
> from MaintenanceRecoveryStage
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
