Hi,
Support case #07249962
For some time now we are getting repeatedly error during the checkpoint removal process from our Wasabi capacity tier. The main error messages are (either one or the other):
Failed to delete checkpoint. Details: HTTP exception: Retrieving message chunk header, error code: 110
Failed to delete checkpoint. Details: Several pending checkpoints found 97,109,
According to the support engineer this should be related to rate limiting of Delete operations on Wasabi's end and he was referring to this URL: https://docs.wasabi.com/docs/setup-limi ... rity%20and
Now I found this post stating their is no such throttling from Wasabi. I guess the support engineer was looking at the wrong API in Wasabi's docs.
Nevertheless we implemented registry keys to reduce S3ConcurrentTaskLimit and limited parallel jobs on the cloud repository to 4. Now the offload performance got bad and I am getting also failed jobs due to resource unavailable timeouts.
I keep working with support on this but nevertheless want to ask, if anybody has seen such error messages before?
Best regards,
Stephan
Support case #07249962
For some time now we are getting repeatedly error during the checkpoint removal process from our Wasabi capacity tier. The main error messages are (either one or the other):
Failed to delete checkpoint. Details: HTTP exception: Retrieving message chunk header, error code: 110
Failed to delete checkpoint. Details: Several pending checkpoints found 97,109,
According to the support engineer this should be related to rate limiting of Delete operations on Wasabi's end and he was referring to this URL: https://docs.wasabi.com/docs/setup-limi ... rity%20and
Now I found this post stating their is no such throttling from Wasabi. I guess the support engineer was looking at the wrong API in Wasabi's docs.
Nevertheless we implemented registry keys to reduce S3ConcurrentTaskLimit and limited parallel jobs on the cloud repository to 4. Now the offload performance got bad and I am getting also failed jobs due to resource unavailable timeouts.
I keep working with support on this but nevertheless want to ask, if anybody has seen such error messages before?
Best regards,
Stephan
Statistics: Posted by StephanF — May 21, 2024 12:17 pm






