You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Creating pools on very large devices can take a very long time.
This was previously handled by allowing the initial call to timeout, followed by an import when the pool is eventually created in the background.
To Reproduce
Steps to reproduce the behavior:
Use very slow device or modify creation code with sleeps.
Perhaps we can use a virtual bdev to simulate this.
Expected behavior
Pool creation should eventually succeed.
OS info (please complete the following information):
MayaStor revision: develop
Additional context
A creation timeout is currently leading into a continuous loop of failed pool creations, requiring us to increase the timeouts.
We can increase the timeout and perhaps we should, but eventually some device will have higher delay, and in that case creation should still eventually complete.
See some related info: openebs/openebs#3805 (comment)
The text was updated successfully, but these errors were encountered:
Describe the bug
Creating pools on very large devices can take a very long time.
This was previously handled by allowing the initial call to timeout, followed by an import when the pool is eventually created in the background.
To Reproduce
Steps to reproduce the behavior:
Use very slow device or modify creation code with sleeps.
Perhaps we can use a virtual bdev to simulate this.
Expected behavior
Pool creation should eventually succeed.
OS info (please complete the following information):
develop
Additional context
A creation timeout is currently leading into a continuous loop of failed pool creations, requiring us to increase the timeouts.
We can increase the timeout and perhaps we should, but eventually some device will have higher delay, and in that case creation should still eventually complete.
See some related info: openebs/openebs#3805 (comment)
The text was updated successfully, but these errors were encountered: