Skip to content
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

could not delete LabelSets (cluster not used) on store-gateway #2636

Closed
heisenbergye opened this issue May 20, 2020 · 4 comments
Closed

could not delete LabelSets (cluster not used) on store-gateway #2636

heisenbergye opened this issue May 20, 2020 · 4 comments

Comments

@heisenbergye
Copy link

Thanos, Prometheus and Golang version used:

thanos version: v0.12.1
promethues version: v2.3.2

Object Storage Provider: minio

What happened:
store

I used a bucket for three clusters' sidecars, after several days, I assigned clusters “ci-prod-cluster-xxx” to another bucket and remove it on querier, but the LabelSets of “cluster=ci-prod-cluster-xxx” on store-gateway wasn't deleted.
And I also retry to restart & re-deploy store-gateway, but it didn‘t work.

What you expected to happen:
the LabelSets of “cluster=ci-prod-cluster-xxx” on store-gateway deleted automatically.

How to reproduce it (as minimally and precisely as possible):

Full logs to relevant components:

Anything else we need to know:

@GiedriusS
Copy link
Member

Hmm, if I understood you correctly then you have removed the Sidecars that have produced those blocks but you still left those blocks in the remote object storage? In such a case, it is expected that they would still show up from Thanos Store since the data is still there. Could you please clarify this?

@heisenbergye
Copy link
Author

@GiedriusS Yes, that's right, I didn't clean up the “ci-prod-cluster-xx” data in the bucket after remove it, because there are too many blocks in the bucket and I don't know which need to be deleted :-( That's very kind of you to tell me how to delete the residual block data.
from the docs block-deletion, it says that deletion-mark.json can help to delete the block that was chosen, but I don't know how to write this file and where to upload.

@stale
Copy link

stale bot commented Jun 20, 2020

Hello 👋 Looks like there was no activity on this issue for last 30 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for next week, this issue will be closed (we can always reopen an issue if we need!). Alternatively, use remind command if you wish to be reminded at some point in future.

@stale stale bot added the stale label Jun 20, 2020
@GiedriusS
Copy link
Member

Just delete the appropriate directories according to their external labels. deletion-mark.json is an internal implementation thing that Thanos uses to mark blocks before their deletion. You could create them yourself by looking at the code to gracefully delete blocks but I don't think this is the way to go forward. I believe this will be properly solved during GSoC. Take a look at this PR: #2780.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants