Hi <#C01HWQ1R0BC|> I'm encountering an issue while setting up SigNoz (self-hosted) with ClickHouse. ...
s
Hi #C01HWQ1R0BC I'm encountering an issue while setting up SigNoz (self-hosted) with ClickHouse. I'm seeing the following error in the logs: `{"level":"error","timestamp":"2025-07-26T053913.451Z","caller":"clickhouseReader/reader.go:3715","msg":"error while reading result","error":"code: 173, message: Couldn't allocate 523 bytes when parsing JSON: while executing 'FUNCTION JSONExtractString(labels : 0, 'service.name' :: 1) -> JSONExtractString(labels, 'service.name') String : 6': While executing MergeTreeSelect(pool: ReadPool, algorithm: Thread)","stacktrace":"github.com/SigNoz/signoz/pkg/query-service/app/clickhouseReader.getPersonalisedError\n\t/home/runner/work/signoz/signoz/pkg/query-service/app/clickhouseReader/reader.go:3715\ngithub.com/SigNoz/signoz/pkg/query-service/app/clickhouseReader.readRowsForTimeSeriesResult\n\t/home/runner/work/signoz/signoz/pkg/query-service/app/clickhouseReader/reader.go:3556\ngithub.com/SigNoz/signoz/pkg/query-service/app/clickhouseReader.(*ClickHouseReader).GetTimeSeriesResultV3\n\t/home/runner/work/signoz/signoz/pkg/query-service/app/clickhouseReader/reader.go:3639\ngithub.com/SigNoz/signoz/pkg/query-service/app/querier/v2.(*querier).execClickHouseQuery\n\t/home/runner/work/signoz/signoz/pkg/query-service/app/querier/v2/querier.go:101\ngithub.com/SigNoz/signoz/pkg/query-service/app/querier/v2.(*querier).runBuilderQuery\n\t/home/runner/work/signoz/signoz/pkg/query-service/app/querier/v2/helper.go:254"}`It seems related to the
JSONExtractString
function. • I'm using the latest SigNoz version (
v0.91.0
) • ClickHouse container is healthy • This happens when trying to view service metrics (query_range calls return 500)
v
There's no memory available to clickhouse:
Copy code
Couldn't allocate 523 bytes when parsing JSON
p
Hey man i solve with this workaround https://github.com/ClickHouse/ClickHouse/issues/66045#issuecomment-2256360306 Dont know if this problem is with my shared vm
v
Interesting
Thanks for sharing