Skip to main content
NetApp Knowledge Base

Openstack: Cinder scheduler uses stale statistics in Active-Active deployments

Last Updated:

Applies to

  • Openstack (all releases)


Cinder scheduler does not make use of a reliable "single source of truth" such as an etcd database.  As such:

  • backend statistics that include total_capacity_gb, provisioned_capacity_gb, max_over_subscription_ratio all reside in memory on each Cinder scheduler.  
  • Volume nodes will periodically send backend statistic updates to the Cinder scheduler nodes
  • However a race condition is possible where:
    • Cinder volumes are created within a few seconds of each other
    • Cinder scheduler statistics are not updated before a new volume create request is received
    • This allows cinder volumes to be created on backing storage pools that should have been filtered by Cinder scheduler (provided that Cinder scheduler had up to data statistics)
      • This could include scenarios where max_over_subscription_ratio is ignored, allowing a backing storage pool to be over provisioned beyond the allowed limit set by max_over_subscription_ratio
      • This could also include a scenario where a nearly full storage pool is selected over a pool with more available space.  

This issue impacts both the generic and NetApp cinder drivers.


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.