In order to associate an `AlertTarget` with specific groups, you would use the `groups` property along with an array of IDs for the groups you care about: { "AlertTarget": { "name": "Administrators", "description": "The Admins", "notification_type": "EMAIL", "groups": [1, 17, 23], ... } } ... View more

It's a timeout problem. The alert is giving the beeline command 60 seconds to spin up a JVM and connect to Hive. You can always go to the Alert's definition in the Ambari UI and change this timeout property to something higher (like 75 seconds). However, before you do that, you might want to run the command yourself and see how long it takes. If it's taking more than a minute, that could indicate a problem with resources on this host. ... View more

Ah, sorry, try /var/log/hadoop-yarn/yarn ... View more

The disk usage alert runs every few minutes. If it hasn't cleared, then perhaps you didn't add enough storage. If you check the message, you can see why it thinks you don't have enough and you can verify your new mounts. The logs would be in /var/log/hadoop/yarn on the ResourceManager host. ... View more

Yes, you can - the above calls can capture it on a host/component basis. ... View more

The is the correct way to check for Maintenance Mode being enabled. Which version of Ambari are you running? When I try this locally, the correct value for `maintenance_state` is reflected. Also - you're putting the ZooKeeper service itself into MM, right? Putting individual hosts/components into MM won't reflect here. ... View more

Let me see if I can help you through this. Can you perform the following query for me: SELECT repo_version_id, version, display_name FROM repo_version ORDER BY version; This will get you a list that looks something like: repo_version_id | version | display_name -----------------+--------------+------------------ 1 | 2.5.0.0-1237 | HDP-2.5.0.0-1237 101 | 2.5.4.0-121 | HDP-2.5.4.0-121 51 | 2.6.0.0-334 | HDP-2.6.0.0-334 Chances are the most recent version is the one that you're on (or are at least supposed to be on). In my case, this is ID 51. So, you would do: UPDATE cluster_version SET state = 'CURRENT' WHERE repo_version_id = 51; The upgrade should work now after making this kind of change. ... View more