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 an in-memory StateBackend #505

Closed
yahoNanJing opened this issue Nov 10, 2022 · 0 comments · Fixed by #523
Closed

Provide an in-memory StateBackend #505

yahoNanJing opened this issue Nov 10, 2022 · 0 comments · Fixed by #523
Labels
enhancement New feature or request

Comments

@yahoNanJing
Copy link
Contributor

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

In some scenarios, there's no requirement of multiple schedulers. And when a scheduler is down, there's no requirement of task recovering and cluster topology recovering. In such cases, an in-memory StateBackend is enough and we don't need to persist the scheduler to the external storage. It's better to provide such kind of option.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant