f1d681875c
If a large volume is backed up or a lot of concurrent backups happen, the cinder-backup service goes offline since a lot of these operations have calls to the C code which are not run on native threads. When many concurrent backup create/restore operations happen, then if all of them are greenthreads, and since, when there is a call to the C code, monkeypatching does not happen by eventlet. Hence, there is no context switch to other threads until the call to the C library is completed. This will block context switching to other green threads. As a result, some of the backup create/restore operations might go to error state. The objects on which read/write operations or C function calls are done are wrapped in Proxy objects so that they run as native threads. Change-Id: I75058c36085eb1a8adb26a95297e3a2039745a2c Closes-Bug: #1745435
Team and repository tags
CINDER
You have come across a storage service for an open cloud computing service. It has identified itself as Cinder. It was abstracted from the Nova project.
- Wiki: https://wiki.openstack.org/Cinder
- Developer docs: https://docs.openstack.org/cinder/latest/
Getting Started
If you'd like to run from the master branch, you can clone the git repo:
For developer information please see HACKING.rst
You can raise bugs here https://bugs.launchpad.net/cinder
Python client
https://git.openstack.org/cgit/openstack/python-cinderclient