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

Provide a command to trigger recovery manually #14700

Closed
fuyufjh opened this issue Jan 20, 2024 · 2 comments · Fixed by #16259
Closed

Provide a command to trigger recovery manually #14700

fuyufjh opened this issue Jan 20, 2024 · 2 comments · Fixed by #16259
Assignees
Milestone

Comments

@fuyufjh
Copy link
Member

fuyufjh commented Jan 20, 2024

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

Sometimes in testing we also hope to test the recovery path beside the normal path.

For example, when creating a streaming job:

  • Normal path uses mutation barrier to update the streaming actors and their topology
  • Recovery path updates the persisted metadata, which would be used to construct the graph upon any recovery

With a SQL (?) command to trigger recovery manually, we may cover this cases better.

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

@github-actions github-actions bot added this to the release-1.7 milestone Jan 20, 2024
@BugenZhao
Copy link
Member

Somehow related to #14438 (comment).

@kwannoel
Copy link
Contributor

kwannoel commented Apr 3, 2024

Not just in testing, but trigger recovery under high barrier latency to let alter rate limit / drop stream job take effect immediately.

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

Successfully merging a pull request may close this issue.

4 participants