ambari-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Hill <greg.h...@RACKSPACE.COM>
Subject Re: COMMERCIAL:Re: GANGLIA broken in Ambari 2.1?
Date Mon, 27 Jul 2015 22:31:49 GMT
I'm aware of Metrics, but Ganglia is in fact still available and from what I read, supported.
 We didn't want to convert over immediately because of the dependence on Hbase/Zookeeper requiring
additional resources on the cluster, and the fact that it's a brand new thing vs something
that's been around and battle-hardened for years.


From: Jayesh Thakrar <<>>
Reply-To: "<>" <<>>,
Jayesh Thakrar <<>>
Date: Monday, July 27, 2015 at 4:16 PM
To: "<>" <<>>
Subject: COMMERCIAL:Re: GANGLIA broken in Ambari 2.1?

Hi Greg,

There's no Ganglia now in Ambari 2.1.

It has been replaced by an internal/local HBase and a metrics collector subsystem.

You will find some details on the wiki.


From: Greg Hill <greg.hill@RACKSPACE.COM<mailto:greg.hill@RACKSPACE.COM>>
To: "<>" <<>>
Sent: Monday, July 27, 2015 3:18 PM
Subject: GANGLIA broken in Ambari 2.1?

In the Centos7 HDP2.3 stack, it attempts to run '/etc/init.d/httpd' which doesn't exist, rather
than using the 'service' shortcut that does still work, even though it forwards to 'systemctl'.
 I injected a script into /etc/init.d/httpd to work around this, but the stack should probably
be fixed.

In the Centos6 HDP2.2 stack, after everything finishes installing Ambari says that Ganglia
Server is down, even though both httpd and gmetad are up and responsive.  You can restart
it fine, and it says it's up for a minute or so, then says it's down.  Processes are still
running, no errors in the logs.  Is this a known issue?  Is there a workaround?

Also, since it now installs the 'ganglia-gmond' package instead of the versioned 'ganglia-gmond-3.5.0',
it gets a conflict with the Centos6 EPEL repo, which has version 3.7 available.  I disabled
the epel repo for now.

I'll try to gather more details and open a JIRA, but just wondered if someone else had run
into this and/or solved it.


View raw message