[
https://issues.apache.org/jira/browse/HELIX-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414712#comment-16414712
]
ASF GitHub Bot commented on HELIX-683:
--------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/helix/pull/162
> Clean monitoring cache upon helix controller enable monitoring
> --------------------------------------------------------------
>
> Key: HELIX-683
> URL: https://issues.apache.org/jira/browse/HELIX-683
> Project: Apache Helix
> Issue Type: Bug
> Reporter: Hao Zhang
> Priority: Major
>
> We found a bug in reporting cluster status, partition masterless duration.
> The root cause is that the duration is calculated based on controller cache.
> And currently, this cache is not cleaned when leadership is changed. As a
> result, if controller A start a mastership handoff but was interrupted once,
> the start time will be kept in cache until next mastership handoff on the
> same partition happens. Then the later handoff duration will be calculated
> based on the stale start time. This could be super large.
> To fix it, we might consider clean cache when leadership changed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
