You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Armando Paniagua (JIRA)" <ji...@apache.org> on 2016/03/23 23:30:25 UTC

[jira] [Created] (AMBARI-15545) ALERTS for yarn_resourcemanager_webui do not work in HA+SSL enabled environment.

Armando Paniagua created AMBARI-15545:
-----------------------------------------

             Summary: ALERTS for yarn_resourcemanager_webui do not work in HA+SSL enabled environment.
                 Key: AMBARI-15545
                 URL: https://issues.apache.org/jira/browse/AMBARI-15545
             Project: Ambari
          Issue Type: Bug
          Components: alerts
    Affects Versions: 2.1.0
            Reporter: Armando Paniagua


ALERTS for yarn_resourcemanager_webui do not work in HA+SSL enabled environment. 

After you enable Resourcemanager HA+SSL through Ambari, the Alert shows Critical for yarn_resourcemanager_webui because the Alert is doing a service check on the wrong URI property. 

If you look at that Alert definition (YARN/alerts.json) you can see the URI describes different yarn-site attributes for non-ssl (http), ssl (https) and high availability. But even after correctly enabling SSL and HA for yarn the Alert for this service still looks at the non-ssl/non-HA attribute:

yarn-site/yarn.resourcemanager.webapp.address

Of course the service check rightfully fails since the resourcemanager webui service is using a different service property which is the high availability https attribute.

I did not see any other similar JIRA reported so I'm wondering if this is a known problem?

 "RESOURCEMANAGER": [
      {
        "name": "yarn_resourcemanager_webui",
        "label": "ResourceManager Web UI",
        "description": "This host-level alert is triggered if the ResourceManager Web UI is unreachable.",
        "interval": 1,
        "scope": "ANY",
        "source": {
          "type": "WEB",
          "uri": {
            "http": "{{yarn-site/yarn.resourcemanager.webapp.address}}",
            "https": "{{yarn-site/yarn.resourcemanager.webapp.https.address}}",
            "https_property": "{{yarn-site/yarn.http.policy}}",
            "https_property_value": "HTTPS_ONLY",
            "kerberos_keytab": "{{yarn-site/yarn.resourcemanager.webapp.spnego-keytab-file}}",
            "kerberos_principal": "{{yarn-site/yarn.resourcemanager.webapp.spnego-principal}}",
            "high_availability": {
              "alias_key" : "{{yarn-site/yarn.resourcemanager.ha.rm-ids}}",
              "http_pattern" : "{{yarn-site/yarn.resourcemanager.webapp.address.{{alias}}}}",
              "https_pattern" : "{{yarn-site/yarn.resourcemanager.webapp.https.address.{{alias}}}}"
            }
          },
          "reporting": {
            "ok": {
              "text": "HTTP {0} response in {2:.3f}s"
            },
            "warning":{
              "text": "HTTP {0} response from {1} in {2:.3f}s ({3})"
            },
            "critical": {
              "text": "Connection failed to {1} ({3})"
            }
          }
        }
      }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)