Clickhouse Container Issue in Docker
TLDR Roberto is struggling with a clickhouse container error in Docker, even after deleting volumes and modifying the `clickhouse-config.xml` file. Pranay inquires about the version of SigNoz being used.
Roberto
Tue, 15 Aug 2023 12:41:31 UTCI uncommented the merge tree and increased the `max_suspicious_broken_parts` in the `clickhouse-config.xml` file to 100 and the service starts normally it was like this: `<merge_tree` `<max_suspicious_broken_parts>100</max_suspicious_broken_parts>` `</merge_tree>`
Pranay
Tue, 15 Aug 2023 12:44:20 UTChey Roberto Which version of SigNoz are you using?
Roberto
Tue, 15 Aug 2023 12:49:41 UTCv0.22.0
SigNoz Community
Indexed 1061 threads
Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI
View in App
Roberto
Tue, 15 Aug 2023 12:12:47 UTCguys I have a problem with the clickhouse container in docker with this error, I deleted all the volumes already but even so when I run `docker compose up -d` this container does not go up