Return-Path: X-Original-To: apmail-ambari-issues-archive@minotaur.apache.org Delivered-To: apmail-ambari-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5AF4E196CB for ; Sat, 9 Apr 2016 03:44:26 +0000 (UTC) Received: (qmail 8647 invoked by uid 500); 9 Apr 2016 03:44:26 -0000 Delivered-To: apmail-ambari-issues-archive@ambari.apache.org Received: (qmail 8610 invoked by uid 500); 9 Apr 2016 03:44:26 -0000 Mailing-List: contact issues-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 issues@ambari.apache.org Received: (qmail 8439 invoked by uid 99); 9 Apr 2016 03:44:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Apr 2016 03:44:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id A880D2C1F68 for ; Sat, 9 Apr 2016 03:44:25 +0000 (UTC) Date: Sat, 9 Apr 2016 03:44:25 +0000 (UTC) From: "Sumit Mohanty (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-15507) Support for Multiple Nameservices 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-15507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-15507: ----------------------------------- Assignee: Henning Kropp > Support for Multiple Nameservices > --------------------------------- > > Key: AMBARI-15507 > URL: https://issues.apache.org/jira/browse/AMBARI-15507 > Project: Ambari > Issue Type: Bug > Affects Versions: trunk > Reporter: Henning Kropp > Assignee: Henning Kropp > Fix For: 2.4.0 > > > This is an umbrella JIRA to collect issues related to the support of multiple Nameservices. > Currently all implementations in Amabari assume that {{hdfs_site\['dfs.nameservices'\]}} is just a string defining one nameservice, while it actually defines multiple nameservices. > Multiple nameservices can be configured for exmaple to support seamless distcp between two HA clusters. > At least 3 issues can be experienced: > # Restart fails, because HdfsResource does not work, related to namenode_ha_utils.py > # (Blueprint) Install fails because DN's register with wrong cluster. How do DN pick the right Nameservice? > # Alerting is broken because it configures namservices as being one nameservice -- This message was sent by Atlassian JIRA (v6.3.4#6332)