Return-Path: X-Original-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 03E7210AB2 for ; Fri, 23 Aug 2013 18:03:54 +0000 (UTC) Received: (qmail 84224 invoked by uid 500); 23 Aug 2013 18:03:53 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 84187 invoked by uid 500); 23 Aug 2013 18:03:53 -0000 Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ambari-dev@incubator.apache.org Delivered-To: mailing list ambari-dev@incubator.apache.org Received: (qmail 84173 invoked by uid 99); 23 Aug 2013 18:03:53 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Aug 2013 18:03:53 +0000 Date: Fri, 23 Aug 2013 18:03:53 +0000 (UTC) From: "Srimanth Gunturi (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-3013) Powering off RM node increases API latency by a factor of 6 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Srimanth Gunturi created AMBARI-3013: ---------------------------------------- Summary: Powering off RM node increases API latency by a factor of 6 Key: AMBARI-3013 URL: https://issues.apache.org/jira/browse/AMBARI-3013 Project: Ambari Issue Type: Bug Components: controller Affects Versions: 1.4.0 Reporter: Srimanth Gunturi Assignee: Mahadev konar Fix For: 1.4.0 On a 4 node cluster I was testing the below API call. {noformat} /api/v1/clusters/${cluster}/services?fields=components/ServiceComponentInfo,components/host_components,components/host_components/HostRoles,components/host_components/metrics/jvm/memHeapUsedM,components/host_components/metrics/jvm/memHeapCommittedM,components/host_components/metrics/mapred/jobtracker/trackers_decommissioned,components/host_components/metrics/cpu/cpu_wio,components/host_components/metrics/rpc/RpcQueueTime_avg_time,components/host_components/metrics/flume/flume,components/host_components/metrics/yarn/Queue {noformat} When everything was working the latency was ~500ms. I then powered off the RM node, and immediately the call latency spiked by 30 times (~15000ms) . After some time, it reduced, but still was 6 times the original latency (~3000ms). When the machine came back online, the call again fell back to its original ~500ms latency. Images attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira