You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2014/07/29 19:06:38 UTC

[jira] [Resolved] (CLOUDSTACK-6318) Cloudstack upgrade takes long time on big cloud_usage databases

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alena Prokharchyk resolved CLOUDSTACK-6318.
-------------------------------------------

    Resolution: Won't Fix

Resolving as won't fix. DB upgrade should be considered to be completed only when both databases - cloud and cloud_usage are updated. If we postpone cloud_usage db upgrade, it can cause all kinds of problems during the usage record updates.

To address "cloud-usage might take longer to update, but is in most of the installation not that critical" - for the environments where usage installation is not critical, this problem - long time update for cloud_usage due to lots of data - won't occur at all. As those environments most likely won't have usage running if usage is irrelevant for them. For the environments where usage matters, we should be consistent with the db upgrade process.

> 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
>            Assignee: Alena Prokharchyk
>            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)