Return-Path: X-Original-To: apmail-ambari-user-archive@www.apache.org Delivered-To: apmail-ambari-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BBAFD1851E for ; Wed, 30 Sep 2015 15:11:43 +0000 (UTC) Received: (qmail 8863 invoked by uid 500); 30 Sep 2015 15:10:45 -0000 Delivered-To: apmail-ambari-user-archive@ambari.apache.org Received: (qmail 8831 invoked by uid 500); 30 Sep 2015 15:10:45 -0000 Mailing-List: contact user-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ambari.apache.org Delivered-To: mailing list user@ambari.apache.org Received: (qmail 8818 invoked by uid 99); 30 Sep 2015 15:10:45 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Sep 2015 15:10:45 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id A7E80C0182 for ; Wed, 30 Sep 2015 15:10:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.999 X-Spam-Level: **** X-Spam-Status: No, score=4.999 tagged_above=-999 required=6.31 tests=[FSL_HELO_BARE_IP_2=1.999, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id lGYvR9yz-IdS for ; Wed, 30 Sep 2015 15:10:38 +0000 (UTC) Received: from relayvx12c.securemail.intermedia.net (relayvx12c.securemail.intermedia.net [64.78.52.187]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 1A72520596 for ; Wed, 30 Sep 2015 15:10:38 +0000 (UTC) Received: from securemail.intermedia.net (localhost [127.0.0.1]) by emg-ca-1-2.localdomain (Postfix) with ESMTP id BD5CB53EBC for ; Wed, 30 Sep 2015 08:10:37 -0700 (PDT) Subject: Re: Removing hard-coded configuration keys for services MIME-Version: 1.0 x-echoworx-msg-id: a4bba3d1-3163-4a1f-9c73-87e8e65ae2e2 x-echoworx-emg-received: Wed, 30 Sep 2015 08:10:37.753 -0700 x-echoworx-action: delivered Received: from 10.254.155.17 ([10.254.155.17]) by emg-ca-1-2 (JAMES SMTP Server 2.3.2) with SMTP ID 266 for ; Wed, 30 Sep 2015 08:10:37 -0700 (PDT) Received: from MBX080-W4-CO-1.exch080.serverpod.net (unknown [10.224.117.101]) by emg-ca-1-2.localdomain (Postfix) with ESMTP id 87F4D53EBC for ; Wed, 30 Sep 2015 08:10:37 -0700 (PDT) Received: from MBX080-W4-CO-1.exch080.serverpod.net (10.224.117.101) by MBX080-W4-CO-1.exch080.serverpod.net (10.224.117.101) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Wed, 30 Sep 2015 08:10:36 -0700 Received: from MBX080-W4-CO-1.exch080.serverpod.net ([10.224.117.101]) by mbx080-w4-co-1.exch080.serverpod.net ([10.224.117.101]) with mapi id 15.00.1044.021; Wed, 30 Sep 2015 08:10:36 -0700 From: Olivier Renault To: "user@ambari.apache.org" , "user@ambari.apache.org" Thread-Topic: Removing hard-coded configuration keys for services Thread-Index: AQHQ+468sdIPfAIufEaG2OvqpFsBg55VLTTf Date: Wed, 30 Sep 2015 15:10:36 +0000 Message-ID: <3824DE340868FCAD.1-8946d15c-6065-498b-8f07-0e38eb8eaf8d@mail.outlook.com> References: <560BF590.2050208@uni.no> In-Reply-To: <560BF590.2050208@uni.no> Accept-Language: en-GB, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-source-routing-agent: Processed Content-Type: multipart/alternative; boundary="_000_3824DE340868FCAD18946d15c6065498b8f070e38eb8eaf8dmailou_" --_000_3824DE340868FCAD18946d15c6065498b8f070e38eb8eaf8dmailou_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable You can remove a service using the API. You'll find the steps at the follow= ing url. https://cwiki.apache.org/confluence/display/AMBARI/Using+APIs+to+delete+a+s= ervice+or+all+host+components+on+a+host Thanks, Olivier On Wed, Sep 30, 2015 at 7:46 AM -0700, "Eirik Thorsnes" > wrote: Hi, I've a cluster with Ambari 2.1.1 and HDP 2.3 stack. I've upgraded the Spark service manually to version 1.5.x from 1.3. I want to remove the (now deprecated) configuration key "spark.yarn.applicationMaster.waitTries" and replace it with another key. Since the key is missing the delete button in the ambari-interface, how can I remove it? Do I have to do it manually in the db, or are there better ways? Regards, Eirik -- Eirik Thorsnes --_000_3824DE340868FCAD18946d15c6065498b8f070e38eb8eaf8dmailou_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

You can remove a service using the API. You'll find the step= s at the following url.

https://cwiki.apache.org/confluence/display/AMBARI/Using+= ;APIs+to+delete+a+service+or+all+host+compo= nents+on+a+host

Thanks,
Olivier




On Wed, Sep 30, 2015 at 7:46 AM -0700, "E= irik Thorsnes" <eirik.thorsnes@uni.no> wrote:

Hi,

I've a cluster with Ambari 2.1.1 and HDP 2.3 stack. I've upgraded the
Spark service manually to version 1.5.x from 1.3.

I want to remove the (now deprecated) configuration key
"spark.yarn.applicationMaster.waitTries" and replace it with anot= her key.

Since the key is missing the delete button in the ambari-interface, how
can I remove it? Do I have to do it manually in the db, or are there
better ways?

Regards,
Eirik

--
Eirik Thorsnes

--_000_3824DE340868FCAD18946d15c6065498b8f070e38eb8eaf8dmailou_--