[
https://issues.apache.org/jira/browse/HELIX-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997869#comment-13997869
]
Zhen Zhang commented on HELIX-444:
----------------------------------
rb:
https://reviews.apache.org/r/21419/
check-in:
https://git-wip-us.apache.org/repos/asf?p=helix.git;a=commit;h=9661fd2f832c904377959ece434e769c34f87f99
> add per-participant partition count gauges to helix
> ---------------------------------------------------
>
> Key: HELIX-444
> URL: https://issues.apache.org/jira/browse/HELIX-444
> Project: Apache Helix
> Issue Type: Improvement
> Reporter: Zhen Zhang
> Assignee: Zhen Zhang
>
> We need a way to pull the known down partition counts out of
> DifferenceWithIdealState when an instance is offline, reducing the alert
> volume to solely the down instance notification. Without metrics from helix
> indicating the number of partitions hosted on a given participant, we can't
> reason as to which "DifferenceWithIdealState" counts are supposed to be down
> and which are an actually difference caused by something other than a node
> outage.
> These should be produced on a per-participant, per-resource basis (ie.,
> helix.i001.participantstatus.cluster.host.db.partitiongauge = 64 or whatever)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
