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 71CFA188B4 for ; Mon, 18 Jan 2016 13:30:40 +0000 (UTC) Received: (qmail 86550 invoked by uid 500); 18 Jan 2016 13:30:40 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 86484 invoked by uid 500); 18 Jan 2016 13:30:40 -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 86418 invoked by uid 99); 18 Jan 2016 13:30:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jan 2016 13:30:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E5A172C1F62 for ; Mon, 18 Jan 2016 13:30:39 +0000 (UTC) Date: Mon, 18 Jan 2016 13:30:39 +0000 (UTC) From: "Hadoop QA (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-14705) nodes in non default config group do no get prompted for restart to update stale configs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-14705?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15= 105281#comment-15105281 ]=20 Hadoop QA commented on AMBARI-14705: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest a= ttachment=20 http://issues.apache.org/jira/secure/attachment/12782790/AMBARI-14705.pat= ch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author= tags. {color:green}+1 tests included{color}. The patch appears to include 1 = new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the = total number of javac compiler warnings. {color:green}+1 release audit{color}. The applied patch does not incre= ase the total number of release audit warnings. {color:red}-1 core tests{color}. The test build failed in ambari-serve= r=20 Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/4957//t= estReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4957/= /console This message is automatically generated. > nodes in non default config group do no get prompted for restart to updat= e stale configs > -------------------------------------------------------------------------= --------------- > > Key: AMBARI-14705 > URL: https://issues.apache.org/jira/browse/AMBARI-14705 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.2.1 > Reporter: Sumit Mohanty > Assignee: Sumit Mohanty > Priority: Critical > Fix For: 2.2.1 > > Attachments: AMBARI-14705.patch > > > I have 2 config groups for hive. 1 with 9 hosts and 1 with 1. The only co= nfig i want different between the 2 config groups is that i want the run co= mpactor to be off on the config group with 1 node. So i created a config gr= oup and turned the value off for that. > Now I made another change to the default query queue=E2=80=99s that i wan= t to be the same for both the config groups. Through the UI it seems like b= oth config groups have them set to the same value but on the actual machine= the are not the same. > PS: Since logging of the bug the hive services on the host in question we= re restarted and thus the stale configs got updated on the host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)