Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Tue, 1 Apr 2014 11:32:16 +0000 (UTC)
From: "Andreas Fuchs (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12705916.1396351861131.42692.1396351936080@arcas>
In-Reply-To: <JIRA.12705916.1396351861131@arcas>
References: <JIRA.12705916.1396351861131@arcas>
Subject: [jira] [Created] (CLOUDSTACK-6318) Cloudstack upgrade takes long
 time on big cloud_usage databases
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Andreas Fuchs created CLOUDSTACK-6318:
-----------------------------------------

             Summary: Cloudstack upgrade takes long time on big cloud_usage databases
                 Key: CLOUDSTACK-6318
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6318
             Project: CloudStack
          Issue Type: Improvement
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Install and Setup
    Affects Versions: 4.2.0
            Reporter: Andreas Fuchs
            Priority: Minor
             Fix For: Future


when updating cloudstack on an environement which is already running for a certain time and has a bigger ammount of instances cloud_usage db will become quite big.

in this situaion the schema updates for the databases can take quite a long time, during this time cloudstack management is offline.

proposal:
cloudstack-managent does only schema updates on cloud db
cloudstack-usage does the scema updates on cloud_usage

this way cloudstack-management will be back online after the update much quicker and only dependant of the size of cloud db

cloud-usage might take longer to update, but is in most of the installation not that critical


--
This message was sent by Atlassian JIRA
(v6.2#6252)