Orphaned shard files can be left behind by retention service [Port to 2.7] #24546
Comments
davidby-influx
added
area/tsm
kind/bug
area/2.x
davidby-influx
added a commit
that referenced
this issue
Jan 5, 2024
…#24547) Under certain circumstances, the retention service can fail to delete shards from the store in a timely manner. When the shard groups are pruned based on age, this leaves orphaned shard files on the disk. The retention service will then not attempt to remove the obsolete shard files because the meta store does not know about them. This can cause excessive disk space usage for some users. This corrects that by requiring shards files be deleted before they can be removed from the meta store. fixes: #24529 (cherry picked from commit 7bd3f89) closes #24545 Co-authored-by: Geoffrey Wossum <gwossum@influxdata.com> (cherry picked from commit 0dc48b1) closes #24546
davidby-influx
added a commit
that referenced
this issue
Jan 5, 2024
…#24547) (#24548) Under certain circumstances, the retention service can fail to delete shards from the store in a timely manner. When the shard groups are pruned based on age, this leaves orphaned shard files on the disk. The retention service will then not attempt to remove the obsolete shard files because the meta store does not know about them. This can cause excessive disk space usage for some users. This corrects that by requiring shards files be deleted before they can be removed from the meta store. fixes: #24529 (cherry picked from commit 7bd3f89) closes #24545 Co-authored-by: Geoffrey Wossum <gwossum@influxdata.com> (cherry picked from commit 0dc48b1) closes #24546
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Port #24545 to 2.7 branch
The text was updated successfully, but these errors were encountered: