Can someone shed some insights on this, whether th...
# support
p
Can someone shed some insights on this, whether this can be resolved via SigNoz https://signoz-community.slack.com/archives/C01HWQ1R0BC/p1737364101298399
s
To recover, increase the limit and then figure out what happened. Override the default values to recover
Copy code
clickhouse:
    files:
        config.d/ch-broken-parts.xml: |
            <clickhouse>
                <merge_tree>
                    <max_suspicious_broken_parts>400</max_suspicious_broken_parts>
                    <max_suspicious_broken_parts_bytes>4,073,741,824</max_suspicious_broken_parts_bytes>
                    <max_suspicious_broken_parts_bytes>4073741824</max_suspicious_broken_parts_bytes>
                </merge_tree>
            </clickhouse>