ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Juanjo Marron <>
Subject Re: Installation custom service the installing clients steps is taking a long time
Date Wed, 25 Oct 2017 18:03:43 GMT
Installing  RPMS is usually the tasks that takes longer in the installation of services in
Other .py script code is usually fast based on my experience.

I would recommend to validate the installation of the RPMS out of ambari Framework. It could
be a yum issue accessing some repo metadata or network slowness downloading  your custom
service RPMS or dependencies from the new repo.
With this installation of rpms independently you could discard the Ambari hypothesis 

Good luck!

    On Wednesday, October 25, 2017 9:45 AM, Chinmay Das <> wrote:

 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 <>

> If you click on the operation where you see the progress bar (you can open
> it from an icon in the top bar if you closed the wizard), you can dig into
> 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 have
> > this issue) with Ambari and HDP 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 eventually
> > goes through and starts and ultimately finishes successfully, there is no
> > information in the logs about what is taking so long. How can I determine
> > what the slow down is?
> > Is there advance logging that can be enabled or a diffirent log I can
> look
> > at?
> >
> > Regards,
> > Chinmay Das
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message