You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@helix.apache.org by "Hao Zhang (JIRA)" <ji...@apache.org> on 2018/03/26 19:11:00 UTC
[jira] [Created] (HELIX-683) Clean monitoring cache upon helix
controller enable monitoring
Hao Zhang created HELIX-683:
-------------------------------
Summary: 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
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)