[jira] [Created] (AMBARI-14848) AMS service has critical alert after upgrade to 2.2.1.0 [METRICS_COLLECTOR:"Connection failed: [Errno -2] Name or service not known to {{zookeeper_clientPort}}:61181" ]

["Aravindan Vijayan (JIRA)" <ji...@apache.org>]

Aravindan Vijayan created AMBARI-14848:
------------------------------------------

             Summary: AMS service has critical alert after upgrade to 2.2.1.0 [METRICS_COLLECTOR:"Connection failed: [Errno -2] Name or service not known to {{zookeeper_clientPort}}:61181" ]
                 Key: AMBARI-14848
                 URL: https://issues.apache.org/jira/browse/AMBARI-14848
             Project: Ambari
          Issue Type: Bug
          Components: ambari-metrics
    Affects Versions: 2.2.1
            Reporter: Aravindan Vijayan
            Assignee: Aravindan Vijayan
            Priority: Critical
             Fix For: 2.2.1


STR: 
# Deploy old version cluster (2.2.0 or 2.0.1)
# Enable Security (Mit)
# Make ambari only upgrade to 2.2.1

Actual results:
AMS service has critical alert after upgrade to 2.2.1.0 [METRICS_COLLECTOR:"Connection failed: [Errno -2] Name or service not known to {{zookeeper_clientPort}}:61181" ]
{code}
    {
      "href" : "https://172.22.68.226:8443/api/v1/clusters/cl1/alerts/18",
      "Alert" : {
        "cluster_name" : "cl1",
        "component_name" : "METRICS_COLLECTOR",
        "definition_id" : 58,
        "definition_name" : "ams_metrics_collector_zookeeper_server_process",
        "host_name" : "os-u14-rxwmxu-upg-sanity-1.novalocal",
        "id" : 18,
        "instance" : null,
        "label" : "Metrics Collector - ZooKeeper Server Process",
        "latest_timestamp" : 1454056914768,
        "maintenance_state" : "OFF",
        "original_timestamp" : 1454055174645,
        "scope" : "ANY",
        "service_name" : "AMBARI_METRICS",
        "state" : "CRITICAL",
        "text" : "Connection failed: [Errno -2] Name or service not known to {{zookeeper_clientPort}}:61181"
      }
{code}

*This issue is present for all OSes and for most upgrade configurations*
*The Issue was not present in* 
2.2.1.0-148
82ac1c302118757378b6d326194a95cef56a8375

*All details are in the alert.json*



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