-
Notifications
You must be signed in to change notification settings - Fork 226
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
Use UNFREEZE TABLE in ClickHouse after backup finished to allow s3 disks unlock and delete remote keys during merge #423
Comments
could you explain what exactly you mean? |
I didn't test that (need to be checked) but it looks like that: If we have s3 disk configured in clickhouse, then freeze command create a 'hardlinks' in shadow dir (both in local FS and in S3) which increment the refcount to the target object. Even if you remove the file from the local filesystem (or move it to backup subfolder), the 'hardlink' in the virtual filesystem (in s3) stays in place. And it don't allow the data files to be deleted after the part go away (because refcount never goes back to zero). There is 'unfreeze' command introduced for that (?) |
got it |
currently when we setup clickhouse:
use_embedded_backup_restore: true s3 disks should be also supported |
We need to be sure we do UNFREEZE to release the files which were freezed.
The text was updated successfully, but these errors were encountered: