Current timeout value for clone volume in the
SolidFire driver is 20 seconds, this is fine
in many cases however there seems to be a
number of customers doing clones of
volumes >= 400G.
A populated 400G volume is taking upwards of
35 seconds to clone in some cases resulting in failure.
There's no reason not to bump this timeout value up
significantly to a worst case scenario (ie multi-terrabyte volume).
Fixes bug: 1202007
Change-Id: I98c399f5d647e14f031018f7fc1cc43bb0d94c84
(cherry picked from commit 9ce7cdbaeb73031d841cb0943ca1812b149d1c19)
Reviewed: https:/ /review. openstack. org/37362 github. com/openstack/ cinder/ commit/ 110133e2a5a90a0 1b983dea5fd8920 10082965a8
Committed: http://
Submitter: Jenkins
Branch: stable/grizzly
commit 110133e2a5a90a0 1b983dea5fd8920 10082965a8
Author: John Griffith <email address hidden>
Date: Tue Jul 16 18:27:19 2013 -0600
Increase timeout period for clone volume.
Current timeout value for clone volume in the
SolidFire driver is 20 seconds, this is fine
in many cases however there seems to be a
number of customers doing clones of
volumes >= 400G.
A populated 400G volume is taking upwards of
35 seconds to clone in some cases resulting in failure.
There's no reason not to bump this timeout value up
significantly to a worst case scenario (ie multi-terrabyte volume).
Fixes bug: 1202007
Change-Id: I98c399f5d647e1 4f031018f7fc1cc 43bb0d94c84 d841cb0943ca181 2b149d1c19)
(cherry picked from commit 9ce7cdbaeb73031