Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-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 9C9B1E13C for ; Wed, 20 Feb 2013 23:13:15 +0000 (UTC) Received: (qmail 61391 invoked by uid 500); 20 Feb 2013 23:13:15 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 61331 invoked by uid 500); 20 Feb 2013 23:13:14 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 61178 invoked by uid 99); 20 Feb 2013 23:13:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Feb 2013 23:13:14 +0000 Date: Wed, 20 Feb 2013 23:13:14 +0000 (UTC) From: "Animesh Chaturvedi (JIRA)" To: cloudstack-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CLOUDSTACK-962) CloudStack usage server didn't store data to cloud_usage in correct time MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-962?page=3Dcom.atla= ssian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-962: ------------------------------------------ Assignee: Kishan Kavala =20 > CloudStack usage server didn't store data to cloud_usage in correct time > ------------------------------------------------------------------------ > > Key: CLOUDSTACK-962 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-962 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the defa= ult.)=20 > Components: Usage > Affects Versions: 4.0.0 > Reporter: Ilia Shakitko > Assignee: Kishan Kavala > Labels: bytesReceived, bytesSended, cloud_usage, usage, user= _statistics > > We have found strange behavior of CloudStack usage server. > There are two global settings values: > usage.stats.job.aggregation.range 1440 > usage.stats.job.exec.time 00:15 > Here I will describe how we had determined this problem. > 9th of January we=E2=80=98ve generated some traffic, like 10Gb. But 10th = of January we didn=E2=80=99t saw records with amount of traffic in cloud_us= age.cloud_usage. And we got this values in cloud_usage db only at 11th. > Looks like it works like as written below: > ---------January---------------------------------9th----------------10th-= -------------11th----------12th----------- > (traffic generetad ) 10Gb 2,5Gb = 5Gb =E2=80=A6 > (traffic stored in usage_db) 0 0 = 10Gb 12,5Gb =E2=80=A6 > We changed the value 'usage.stats.job.aggregation.range' to 10 minutes to= have more tests. Here's what we got: > ---------Timeline--------------------------------10:00--------------10:10= ------------10:20--------10:30--------10:40 > (traffic generetad ) 5Gb 0 = 2,5Gb 0 0 > (traffic stored in usage_db) 0 0 = 5Gb 5Gb 7,5Gb > My colleague Wei Zhou will adds more comments with what we found in Cloud= Stack source and solution for it. > Will keep updated information about tests and additional info in this thr= ead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira