Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D2A59200CAE for ; Wed, 7 Jun 2017 03:38:28 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D1A58160BD3; Wed, 7 Jun 2017 01:38:28 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 23B1C160BC6 for ; Wed, 7 Jun 2017 03:38:27 +0200 (CEST) Received: (qmail 60467 invoked by uid 500); 7 Jun 2017 01:38:27 -0000 Mailing-List: contact issues-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 issues@ambari.apache.org Received: (qmail 60458 invoked by uid 99); 7 Jun 2017 01:38:25 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jun 2017 01:38:25 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 5FCEF1822E2 for ; Wed, 7 Jun 2017 01:38:25 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id GV1IrrPOeIhn for ; Wed, 7 Jun 2017 01:38:24 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 70A635F5B8 for ; Wed, 7 Jun 2017 01:38:24 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 04375E0DA7 for ; Wed, 7 Jun 2017 01:38:19 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 410FE21E12 for ; Wed, 7 Jun 2017 01:38:18 +0000 (UTC) Date: Wed, 7 Jun 2017 01:38:18 +0000 (UTC) From: "Alejandro Fernandez (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-19962) Clicking on the login button (or hitting page refresh) to see the dashboard takes a while on a 1000-node cluster MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 07 Jun 2017 01:38:29 -0000 [ https://issues.apache.org/jira/browse/AMBARI-19962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19962: ----------------------------------------- Summary: Clicking on the login button (or hitting page refresh) to see the dashboard takes a while on a 1000-node cluster (was: Clicking on the login button (or hitting page refresh) to seeing the dashboard takes a while on a 1000-node cluster) > Clicking on the login button (or hitting page refresh) to see the dashboard takes a while on a 1000-node cluster > ---------------------------------------------------------------------------------------------------------------- > > Key: AMBARI-19962 > URL: https://issues.apache.org/jira/browse/AMBARI-19962 > Project: Ambari > Issue Type: Bug > Components: ambari-web > Affects Versions: 2.5.0 > Reporter: Andrii Tkach > Assignee: Andrii Tkach > Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19962_branch-2.5.patch, AMBARI-19962.patch > > > Log in to Dashboard is really slow (about 15 seconds on a 1000-node cluster). This does not include the time to load the widget graphs (loading the widget takes additional ~5 seconds on top). > Eliminate some of the bottlenecks and make this faster. -- This message was sent by Atlassian JIRA (v6.3.15#6346)