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 C9E16176CA for ; Tue, 20 Jan 2015 18:39:34 +0000 (UTC) Received: (qmail 24556 invoked by uid 500); 20 Jan 2015 18:39:34 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 24512 invoked by uid 500); 20 Jan 2015 18:39:34 -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 24500 invoked by uid 99); 20 Jan 2015 18:39:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Jan 2015 18:39:34 +0000 Date: Tue, 20 Jan 2015 18:39:34 +0000 (UTC) From: "Antonenko Alexander (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-9219) HDFS should not need restart after adding second Hive component 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-9219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-9219: ---------------------------------------- Attachment: prop-host-switch.tiff > HDFS should not need restart after adding second Hive component > --------------------------------------------------------------- > > Key: AMBARI-9219 > URL: https://issues.apache.org/jira/browse/AMBARI-9219 > Project: Ambari > Issue Type: Bug > Components: ambari-web > Affects Versions: 2.0.0 > Reporter: Antonenko Alexander > Assignee: Antonenko Alexander > Priority: Critical > Fix For: 2.0.0 > > Attachments: prop-host-switch.tiff > > > 1) I added a second Hive Metastore, which also updates the proxyuser for hcat to core-site > 2) this requires a restart to NN and SNN, which is OK > 3) then I went to add a second HiveServer2, that again updates the proxyuser, just switches the order of the existing hosts in the property. > 4) that property change should not have happened. There is no reason to force another restart when the host list is not actually changing. So on property update, we should not make the change if the host list is effectively the same. > See screen shot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)