Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5336C1896F for ; Mon, 23 Nov 2015 03:24:11 +0000 (UTC) Received: (qmail 68849 invoked by uid 500); 23 Nov 2015 03:24:11 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 68808 invoked by uid 500); 23 Nov 2015 03:24:11 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 68773 invoked by uid 99); 23 Nov 2015 03:24:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Nov 2015 03:24:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id ED38F2C044E for ; Mon, 23 Nov 2015 03:24:10 +0000 (UTC) Date: Mon, 23 Nov 2015 03:24:10 +0000 (UTC) From: "Hadoop QA (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-14007) Fix precision issues in AMS. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-14007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021451#comment-15021451 ] Hadoop QA commented on AMBARI-14007: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12773747/AMBARI-14007.patch against trunk revision . {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4368//console This message is automatically generated. > Fix precision issues in AMS. > ---------------------------- > > Key: AMBARI-14007 > URL: https://issues.apache.org/jira/browse/AMBARI-14007 > Project: Ambari > Issue Type: Bug > Affects Versions: 2.1.2 > Reporter: Aravindan Vijayan > Assignee: Aravindan Vijayan > Priority: Critical > Fix For: 2.1.3 > > Attachments: AMBARI-14007.patch > > > Problem > The following error is seen in the ambari server log when different time periods are selected in the Host page. > 19 Nov 2015 22:27:50,476 ERROR [qtp-client-79] MetricsRequestHelper:96 - Error getting timeline metrics : {"exception":"BadRequestException","message":"java.lang.Exception: Requested precision (SECONDS) for given time range causes result set size of 15840, which exceeds the limit - 11520. Please request higher precision.","javaClassName":"org.apache.hadoop.yarn.webapp.BadRequestException"} > Bug > The default metric service result limit of 11520 was not able to satisfy a couple of specific cases of 22 host metrics requested for 2 hours in SECONDS precision. > Fix > Change default limit to15840. Covers all time periods of all metric charts in Ambari web. Introduce a simple 1 time retry mechanism in Ambari server according to which the server retries AMS with the same request with higher precision if a request fails due to PrecisionLimitExceededException. -- This message was sent by Atlassian JIRA (v6.3.4#6332)