cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wido den Hollander (JIRA)" <>
Subject [jira] [Closed] (CLOUDSTACK-7641) Do not always ask libvirt to refresh storage pools
Date Sun, 28 Sep 2014 22:42:34 GMT


Wido den Hollander closed CLOUDSTACK-7641.
    Resolution: Fixed

Merged into master

> Do not always ask libvirt to refresh storage pools
> --------------------------------------------------
>                 Key: CLOUDSTACK-7641
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: Future
>            Reporter: Wido den Hollander
>            Assignee: Wido den Hollander
>            Priority: Minor
>              Labels: ceph, libvirt, rbd
>             Fix For: 4.5.0
> When getStoragePool() in the LibvirtStorageAdapter is called it asks libvirt for information
regarding that storage pool.
> In the process the StorageAdapter asks libvirt to 'refresh' the storage pool.
> Refreshing a storage pool means that libvirt will scan the whole pool and get information
about all the volumes which it then caches.
> getStoragePool() is called for almost every storage operation in KVM and that causes
> On big (RBD) storage pools such a refresh can take up to 2 or 3 minutes.
> The StatsCollector in the Management Server asks all the hosts about the storage pools
as well, so we should only refresh the pool when the StatsCollector wants storage statistics.
> This way we keep the information in libvirt up to date, but we also speed up storage
tasks on KVM.

This message was sent by Atlassian JIRA

View raw message