-
Notifications
You must be signed in to change notification settings - Fork 520
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
feat: Allow to set max_suspicious_broken_parts in merge_tree settings… #1080
feat: Allow to set max_suspicious_broken_parts in merge_tree settings… #1080
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Could you please upgrade the minor version of the chart instead?
@@ -165,6 +165,7 @@ data: | |||
<parts_to_delay_insert>{{ .Values.clickhouse.configmap.merge_tree.parts_to_delay_insert }}</parts_to_delay_insert> | |||
<parts_to_throw_insert>{{ .Values.clickhouse.configmap.merge_tree.parts_to_throw_insert }}</parts_to_throw_insert> | |||
<max_part_loading_threads>{{ .Values.clickhouse.configmap.merge_tree.max_part_loading_threads }}</max_part_loading_threads> | |||
<max_suspicious_broken_parts>100</max_suspicious_broken_parts> | |||
</merge_tree> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This shouldn't be hardcoded.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right, I will fix it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possible to push a change for this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR created.
A few days ago I faced a problem in one of our clickhouse replicas. When clickhouse tries to init db it needs to merge broken parts of data to a single partition and it needs to delete those files afterward. If the number of those files exceeded the number set in the configuration it denied deletion (here) and db doesn't init, so what we need to do is increase the max_suspicious_broken_parts value to cover those broken file numbers.
Unfortunately, it is not possible to set the above settings via chart values so I decided to add handling these specific params.