From dev-return-61292-apmail-ambari-dev-archive=ambari.apache.org@ambari.apache.org Mon Mar 2 14:38:27 2015 Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 17992173CF for ; Mon, 2 Mar 2015 14:38:27 +0000 (UTC) Received: (qmail 1140 invoked by uid 500); 2 Mar 2015 14:38:05 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 1098 invoked by uid 500); 2 Mar 2015 14:38:05 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 1086 invoked by uid 99); 2 Mar 2015 14:38:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Mar 2015 14:38:04 +0000 Date: Mon, 2 Mar 2015 14:38:04 +0000 (UTC) From: "Jonathan Hurley (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMBARI-9848) Alerts Need HA Mode Dynamic Property Support For WEB and METRIC MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-9848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley resolved AMBARI-9848. ------------------------------------- Resolution: Fixed > Alerts Need HA Mode Dynamic Property Support For WEB and METRIC > --------------------------------------------------------------- > > Key: AMBARI-9848 > URL: https://issues.apache.org/jira/browse/AMBARI-9848 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-server > Affects Versions: 2.0.0 > Reporter: Jonathan Hurley > Assignee: Jonathan Hurley > Fix For: 2.0.0 > > Attachments: AMBARI-9848.patch > > > Alerts for services that support a standard HA mode (nameservice and/or alias) need to be able to understand how to calculate the correct server to contact. This means building a dynamic key to use when discovering the URL to use for METRIC and WEB alerts. > The proposal is to add a new child element to the URL parameter: > {code} > "high_availability": { > "nameservice": "{{hdfs-site/dfs.nameservices}}", > "alias_key" : "{{hdfs-site/dfs.ha.namenodes.{{ha-nameservice}}}}", > "http_pattern" : "{{hdfs-site/dfs.namenode.http-address.{{ha-nameservice}}.{{alias}}}}", > "https_pattern" : "{{hdfs-site/dfs.namenode.https-address.{{ha-nameservice}}.{{alias}}}}" > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)