Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id AB242200D27 for ; Wed, 25 Oct 2017 20:03:59 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A99A4160BDA; Wed, 25 Oct 2017 18:03:59 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id EE6191609CE for ; Wed, 25 Oct 2017 20:03:58 +0200 (CEST) Received: (qmail 24096 invoked by uid 500); 25 Oct 2017 18:03:57 -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 24084 invoked by uid 99); 25 Oct 2017 18:03:57 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Oct 2017 18:03:57 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id DC8391807C5 for ; Wed, 25 Oct 2017 18:03:56 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.694 X-Spam-Level: X-Spam-Status: No, score=0.694 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_MUA_MOZILLA=1.596, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id NB6xbkEsf_j1 for ; Wed, 25 Oct 2017 18:03:54 +0000 (UTC) Received: from sonic312-22.consmr.mail.ne1.yahoo.com (sonic312-22.consmr.mail.ne1.yahoo.com [66.163.191.203]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 1214C5FB4E for ; Wed, 25 Oct 2017 18:03:53 +0000 (UTC) X-YMail-OSG: znzjHWgVM1k3bBn3iZ5e6Jq5h4.ATecGdji9Zg8kWQDCtLh0GoXeMxYF5e8G1QT g2ZOQo3fh0CKEG6t89GjR0Ar3B6JqzlujOuUEMBM5c_LTdGWsCIoMSPwXcnrNqnD8UGGmTXBkz2P 7W81GFHVu6MrOLpL.wvsWbKbOlYoTwZqk472evADT5KGIYZXUlSPy1Sx5K_ZBhTrmrqYF_JznxyT UrqK2ZRZtl7.QETsZ4iqGa9C.5KmnNbgFMqfYnyX2iMjaAPMxf0xZEEmO77j3EdwX8mdDpIcSHZK m_EDYfd5fJVYHz8TBsVuO6bEY97_Aw0VA80A9mpEsfqqUXs2JPImxgINM7NeYsQLoc9LUOpUa.vU 9HXOkQhAsnBpmMR7PGzbmDms01bHBlzuHdB5132IjF.0TnEukv2W2ceMd2xANjxVUuQwwo9ZIaln dwspv3wVKj5BUk9EQrdb64uuMo2c5xvbIZsNvY6xGaL4Vn74HLIqiRsN8.5I- Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.ne1.yahoo.com with HTTP; Wed, 25 Oct 2017 18:03:46 +0000 Date: Wed, 25 Oct 2017 18:03:43 +0000 (UTC) From: Juanjo Marron Reply-To: Juanjo Marron To: "dev@ambari.apache.org" Message-ID: <200050116.4314676.1508954623855@mail.yahoo.com> In-Reply-To: References: Subject: Re: Installation custom service the installing clients steps is taking a long time MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4314675_1872485655.1508954623853" X-Mailer: WebService/1.1.10801 YahooMailNeo Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:56.0) Gecko/20100101 Firefox/56.0 archived-at: Wed, 25 Oct 2017 18:03:59 -0000 ------=_Part_4314675_1872485655.1508954623853 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Installing=C2=A0 RPMS is usually the tasks that takes longer in the install= ation of services in Ambari. Other .py script code is usually fast based on my experience. I would recommend to validate the installation of the RPMS out of ambari Fr= amework. It could be a yum issue accessing some repo metadata or network sl= owness downloading=C2=A0 your custom service RPMS or dependencies from the = new repo. With this installation of rpms independently you could discard the Ambari h= ypothesis=20 Good luck! =20 On Wednesday, October 25, 2017 9:45 AM, Chinmay Das wrote: =20 This is the problem, The process stdout and stderr shows empty. The deployment of my custom service eventually succeeds but its taking way too long than usual. This happens only in 4 node clusters or more, for example, earlier if I was able to deploy the service in (say) 10 mins, Now its taking like 45 mins for the same. The progress bar goes on hold, and I cant see any logs on ambari UI even after opening log wizard. On Wed, Oct 25, 2017 at 9:24 PM, Gonzalo Herreros wrote: > If you click on the operation where you see the progress bar (you can ope= n > it from an icon in the top bar if you closed the wizard), you can dig int= o > the operation, host and finally action to see the process stdout and > stderr. > That's the lowest level of the component script execution you can get, > other than debugging the python code. > > Gonzalo > > On 25 October 2017 at 15:46, Chinmay Das wrote: > > > Hi, > > > > I am trying to use 4 node or more than that (3 nodes or less dosent hav= e > > this issue) with Ambari 2.5.0.3 and HDP 2.6.2.0 for installation of a > > custom service on ambari. > > But during install the installing clients steps is taking a long time, > the > > progress bar does not advance for several minutes, the process eventual= ly > > goes through and starts and ultimately finishes successfully, there is = no > > information in the logs about what is taking so long. How can I determi= ne > > what the slow down is? > > Is there advance logging that can be enabled or a diffirent log I can > look > > at? > > > > Regards, > > Chinmay Das > > > =20 ------=_Part_4314675_1872485655.1508954623853--