-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disk creation/deletion takes more than 30 seconds #7188
Comments
A more recent example from a Terraform destroy operation of 20 instances and their boot disks (concurrency = 10). This one took minutes:
|
Here is the
Here is the
|
Looking at saga The first is:
That saga node only has a call to The second is:
In the volume delete saga, the Looking into the log messages posted earlier in this issue:
This indicates to me that it's spending a significant amount of time recording the saga node success, after having deleted three regions within about a second of the saga node starting. |
This particular database update alone can take up to 6+ seconds (found this as I used dtrace to get the database transaction latencies):
|
On rack2 after upgrading to 37c7f18, disk deletion times took even longer. The
|
Hitting this with
The one that jumps out is |
Quick followup that might raise more questions than answers; I tried running this under
What I can't explain is the query time - 92ms seems perfectly reasonable for reading ~40,000 rows, I guess, but what could possibly have made that same query take 73 seconds in production? |
Disk creation and deletion is substantially slower on rack2 since it was updated to commit
e7d32ae2375b0231193f1dc84271f900915b2d6b
. I was waiting for crucible#1571 and crucible#1572 to be fixed/root-caused before conflating this issue with other underlying problems. But after updating to commit 41d7c9b, the problem still persists.I'll add some of the saga examples. Here is a delete disk saga I was looking at yesterday which took 34 seconds to complete:
I'll add some other even longer-running ones from the latest build.
The text was updated successfully, but these errors were encountered: