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

Describe verify/repair commands #270

Closed
bwplotka opened this issue Apr 6, 2018 · 4 comments
Closed

Describe verify/repair commands #270

bwplotka opened this issue Apr 6, 2018 · 4 comments

Comments

@bwplotka
Copy link
Member

bwplotka commented Apr 6, 2018

  • How to use it
  • How to extend/modify it
  • What is that for
domgreen added a commit that referenced this issue May 22, 2018
* #270 add docs for the bucket component and its sub commands

* removing -r in examples
@domgreen
Copy link
Contributor

@Bplotka can I close down this issue?

@bwplotka
Copy link
Member Author

Not really. We need to also describe all of the verify/repair "issues" we have: https://github.com/improbable-eng/thanos/blob/master/cmd/thanos/bucket.go#L25 but you can leave that to me. You did the major part though, thanks!

@jabbrwcky
Copy link
Contributor

Also the documentation should specify prerequisites for running verifier.

I stumbled across the log message GLOBAL COMPACTOR SHOULD __NOT__ BE RUNNING ON THE SAME BUCKET issued by the verifier, and was wondering if my setup is wrong.

I dug a little bit and found that this message is a blanket message output here:

level.Warn(v.logger).Log(

There is no documentation or any easily identifiable issue that explains the why of this message.

I assume that the verifier with repair enabled should not run concurrently with the compactor, but this is just a guess.

I think that running the verifier read-only with a running compactor should not have negative impact, in which case it might be enough to show this message only if repairs are enabled.

In any case the documentation should refelect when to stop the compactor before running verify.

@stale
Copy link

stale bot commented Feb 7, 2020

This issue/PR has been automatically marked as stale because it has not had recent activity. Please comment on status otherwise the issue will be closed in a week. Thank you for your contributions.

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

3 participants