[
https://issues.apache.org/jira/browse/AMBARI-23445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16431994#comment-16431994
]
Hudson commented on AMBARI-23445:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9023 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9023/])
AMBARI-23445. Refactor metrics_alert to support multiple nameservices
(6454655+adoroszlai:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=09c959dba7622d0428931e87262f35a580fa3c14])
* (edit)
ambari-server/src/test/python/stacks/2.0.6/HDFS/test_alert_metrics_deviation.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/namenode_ha_utils.py
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_metrics_deviation.py
> Refactor metrics_alert to support multiple nameservices
> -------------------------------------------------------
>
> Key: AMBARI-23445
> URL: https://issues.apache.org/jira/browse/AMBARI-23445
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.7.0
> Reporter: Endre Major
> Assignee: Endre Major
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> The HDFS metrics based alerts defined in alert_metrics_deviation.py is
> agnostic of federated Namenodes.
> Tasks:
> When federation is enabled we should add an alert instance per nameservice
> for the HDFS metric based alerts.
> Currently, we track metrics based alerts for:
> RPC processing latency
> RPC queue latency
> NN Heap usage
> There are multiple alerts based on whether service port is enabled and also
> different time windows.
> For every alert type, there should be an instance of the alert per
> nameservice.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
