Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 72FF017A35 for ; Wed, 26 Aug 2015 10:18:46 +0000 (UTC) Received: (qmail 19203 invoked by uid 500); 26 Aug 2015 10:18:46 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 19170 invoked by uid 500); 26 Aug 2015 10:18:46 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 19161 invoked by uid 500); 26 Aug 2015 10:18:46 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 19157 invoked by uid 99); 26 Aug 2015 10:18:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Aug 2015 10:18:46 +0000 Date: Wed, 26 Aug 2015 10:18:46 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-8761) Management server heartbeat takes too long to finish 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/CLOUDSTACK-8761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712885#comment-14712885 ] ASF GitHub Bot commented on CLOUDSTACK-8761: -------------------------------------------- Github user miguelaferreira commented on the pull request: https://github.com/apache/cloudstack/pull/730#issuecomment-134934893 @ustcweizhou good catch! The idea of that script was to be a simple collection of git commands and assumed that people already understood git. But then we iterated many times over it, adding more and more logic to make it "easier to use". The issue you just bumped into is the downside: the script became to tied up in small details! We should fix this structurally in the script. > Management server heartbeat takes too long to finish > ---------------------------------------------------- > > Key: CLOUDSTACK-8761 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8761 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Reporter: Wei Zhou > Assignee: Wei Zhou > > We got a lot of debug message in management-server.log every 1.5 seconds. > The cluster.heartbeat.interval is set to 1500 by default. As it was not changed after its first commit, so I think it is 1500 ms. > However, The durations are less than 10ms actually. > 2015-08-18 00:00:04,526 DEBUG [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-047bb88f) Management server heartbeat takes too long to finish. profiler: Done. Duration: 4ms, profilerHeartbeatUpdate: Done. Duration: 3ms, profilerPeerScan: Done. Duration: 0ms > 2015-08-18 00:00:06,036 DEBUG [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-68018e26) Peer scan takes too long to finish. profiler: Done. Duration: 0ms, profilerQueryActiveList: Done. Duration: 0ms, profilerSyncClusterInfo: Done. Duration: 0ms, profilerInvalidatedNodeList: Done. Duration: 0ms, profilerRemovedList: Done. Duration: 0ms -- This message was sent by Atlassian JIRA (v6.3.4#6332)