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

Metastore Recovery on Command Topic Failure #5569

Closed
agavra opened this issue Jun 8, 2020 · 2 comments
Closed

Metastore Recovery on Command Topic Failure #5569

agavra opened this issue Jun 8, 2020 · 2 comments
Labels
enhancement P0 Denotes must-have for a given milestone

Comments

@agavra
Copy link
Contributor

agavra commented Jun 8, 2020

Is your feature request related to a problem? Please describe.

In a recent production issue, the command topic was lost due to user-error (setting the retention of the topic to 0) and we were unable to recover the data and recreate the queries.

Describe the solution you'd like

We should have some lightweight, last-ditch mechanism to recover from loss of the command topic. One solution is to persist the metastore/command-topic to a file with a checksum and use that to manually re-issue statements if necessary.

Describe alternatives you've considered

Open to suggestions.

@agavra agavra added enhancement needs-triage P0 Denotes must-have for a given milestone labels Jun 8, 2020
@blueedgenick
Copy link
Contributor

if you've failed to secure the environment against this kind of mistake, and are concerned about it happening, there are general solutions to this ? e.g. use Connect to sink the command topic to a file in s3

@agavra
Copy link
Contributor Author

agavra commented Jun 24, 2020

closing as duplicate of #5575

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement P0 Denotes must-have for a given milestone
Projects
None yet
Development

No branches or pull requests

3 participants