You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@helix.apache.org by "Hunter L (JIRA)" <ji...@apache.org> on 2019/02/27 18:52:00 UTC

[jira] [Resolved] (HELIX-812) HELIX: Fix maintenance history bug

     [ https://issues.apache.org/jira/browse/HELIX-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hunter L resolved HELIX-812.
----------------------------
    Resolution: Fixed

> 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)