Member since
10-14-2015
165
Posts
63
Kudos Received
27
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2060 | 12-11-2018 03:42 PM | |
1758 | 04-13-2018 09:17 PM | |
1175 | 02-08-2018 06:34 PM | |
2885 | 01-24-2018 02:18 PM | |
7206 | 10-11-2017 07:27 PM |
06-21-2016
10:19 PM
1 Kudo
It needs to take a static value from the /etc/ambari-server/conf/ambari.properties file. You need to add this and restart: ambari.display.url = http://www.myserver.com
... View more
06-13-2016
08:48 PM
Well, it seems like AMS metrics aren't consumable by Ambari until version 2.4.0 comes out: https://issues.apache.org/jira/browse/AMBARI-15766 This means that JMX metrics are the only ones which work by default and I don't think Kafka exposes them. You could use a third-party plugin which exposes them, but that's probably not ideal. So, it seems like to monitor Kafka metrics today you'd need to write a SCRIPT based alert which would check a specific metric from AMS. You could write a single, generic SCRIPT alert which takes the metric to check as a parameter. This way, you'd create several different alert definitions (1 for each metric) and then re-use the same Python script. If you wanted to expose Kafka metrics via JMX, once of these might help: https://cwiki.apache.org/confluence/display/KAFKA/JMX+Reporters You'd expose JMX via Kafka and then expose that JMX data via something like JMXtrans which alerts could consume. Or, you could wait for Ambari 2.4.0 which should let you consume AMS metrics natively and just write a simple alert definition for it.
... View more
06-13-2016
07:05 PM
1 Kudo
You can definitely create new alerts using the REST APIs, but this is not exposed in the web client yet: https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/alert-definitions.md#api-summary With that said, can you provide the mechanism through which things like "Under Replicate Counts" are exposed through Kafka? If they are JMX or AMS metrics, you can create a METRIC alert to monitor them.
... View more
06-08-2016
12:08 PM
1 Kudo
We'd also need to see the last section of /var/log/ambari-server/ambari-server.log
... View more
05-16-2016
06:54 PM
1 Kudo
Wow ... that's a problem with the RPMs I think. Here's how to fix it: rm -r /usr/hdp/current/zookeeper-server
ln -s /usr/hdp/2.2.9.0-3393/zookeeper /usr/hdp/current/zookeeper-server
... View more
05-16-2016
04:03 PM
This is saying that you're missing either a ZK file or ZK symlink. Can you post the output of ls -l /usr/hdp/current | grep zookeeper
ls -l /usr/hdp/current/zookeeper-server/bin
... View more
05-16-2016
12:34 PM
If you have Kerberos enabled, you might be hitting: https://issues.apache.org/jira/browse/AMBARI-14847 You can upgrade to Ambari 2.2.2 and that should resolve the issue.
... View more
05-04-2016
12:39 PM
1 Kudo
There's already an alert which monitors this for you. It's called the NameNode Last Checkpoint alert.
... View more
04-18-2016
06:11 PM
Yes, that should also work. You'll want to PUT the entire JSON back, not just the 1 changed line. How interesting - that seems like a bug that it's still using the older value on clean 2.4 installs.
... View more
04-18-2016
12:51 PM
Yes, this is why I suggested you check both kafka-broker/port and kafka-broker/listeners. Changing the default port is fine for now, but if you ever change the port again, you'll need to repeat this step. Instead, it's better to either set kafka-broker/port or change the alert to use kafka-broke/listeners. I'm guessing that at one point this was an HDP 2.2 cluster (which used kafka-broker/port originally) and then it was upgraded to an HDP 2.3 cluster.
... View more
- « Previous
- Next »