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.

Sign up for GitHub

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

Jump to bottom

Persistent SQL blacklist #55013

Open
1 task done
SHaaD94 opened this issue Jan 13, 2025 · 0 comments · Fixed by #55014
Open
1 task done

Persistent SQL blacklist #55013

SHaaD94 opened this issue Jan 13, 2025 · 0 comments · Fixed by #55014
Labels
type/feature-request version:3.5

Comments

@SHaaD94
Copy link
Contributor

SHaaD94 commented Jan 13, 2025 •
edited by wanpengfei-git
Loading

Feature request

Is your feature request related to a problem? Please describe.
Currently it is inconvenient to use SQL blacklist in production, since it is stored purely in memory, not synchronized between instances. In case of redeploy or even FE OOM all blacklist is reset and requires addition again.

Describe the solution you'd like
Store SQL blacklist as meta image. Replicate changes through the edit log.

Describe alternatives you've considered
Other alternatives would be hacks around init containers in k8s / side scripts.

Additional context
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/feature-request version:3.5
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Feature] Make blacklist persistent SHaaD94/starrocks
2 participants
@SHaaD94 @wanpengfei-git