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
wal-g delete retain taking time and then timing out #1644
Comments
Thanks for the report! Can you plz kill it with SIGABRT during such wait? It will pring gorountines so we can conclude what's going on. I bet it's listing WALs... |
Below is the output of SIGABRT
I added debug logging and below are the last few lines of the output where it is hung
|
Hi @x4m , Do you see any issues with the goroutines and the debug log? The issue started after we added postgres majorversion in the bucket path as recommended in various Issues. Thanks, |
Well, it’s listing objects to choose which to delete. It’s legitimate operation.We do not have much options but increase a timeout. What we can do on wal-g side is to delete in smaller chunks, so that several calls to ‘’’wal-g delete’’’ will finally do the job.--Отправлено из мобильной Яндекс Почты19.02.2024, 09:43, "nikhil-postgres" ***@***.***>:
Hi @x4m , Do you see any issues with the goroutines and the debug log?
Thanks,
Nikhil
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Got it. What we can do on wal-g side is to delete in smaller chunks, so that several calls to ‘’’wal-g delete’’’ will finally do the job |
Hi @x4m , Is there any parameter to increase the timeout parameter for listing backup? I see only WALG_STOP_BACKUP_TIMEOUT which is used during pg_stop_backup Thanks, |
PostgreSQL: 13.6
WAL-G: wal-g version v1.1.2-rc
Issue description
For highly transactional databases, we have seen than wal-g delete retain FIND_FULL is taking lot of time and then times out.
Describe your problem
Attaching strace output
Logs
The text was updated successfully, but these errors were encountered: