helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kanak Biscuitwala (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (HELIX-444) add per-participant partition count gauges to helix
Date Mon, 25 Aug 2014 17:34:59 GMT

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

Kanak Biscuitwala reopened HELIX-444:

> 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
>             Fix For: 0.7.1, 0.6.4
> 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

View raw message