https://signoz.io logo
Join Slack
Powered by
Migration help to v0.88.1 needed :pray: I just bum...
# support
o
Migration help to v0.88.1 needed 🙏 I just bumped version from v0.77 to the latest version and noticed that there was a migration guide for 0.88 to change from normalized to unnormalized metric names. I run a standalone deployment without any modifications. The normal upgrade went fine by pulling main and running the installer and all 4 docker containers are up and running after. But following the guide https://signoz.io/docs/operate/migration/upgrade-0.88#docker-standalone to add the migration-job and then running it failed with error in log. I modified signoz/deploy/docker/docker-compose.yaml and added the part from guide to services: section. I changed CH_ADDR to "signoz-clickhouse:9000" (not sure if this is correct, but signoz-clickhouse is the container name of the clickhouse service). I left the rest as is and then ran 
docker-compose up -d migration-job
Logs from this command are:
Copy code
docker-compose logs -f migration-job
WARN[0000] /root/signoz/deploy/docker/docker-compose.yaml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
migration-job-1  | {"level":"error","ts":1751879720.45815,"caller":"migrate/main.go:283","msg":"data migration failed: error building metric details: error checking metric otelcol_receiver_accepted_metric_points → otelcol_receiver_accepted_metric_points: code: 173, message: Couldn't allocate 325 bytes when parsing JSON: while executing 'FUNCTION JSONExtractKeys(labels :: 0) -> JSONExtractKeys(labels) Array(String) : 1'","stacktrace":"main.main\n\t/go/src/github.com/signoz/migrate/main.go:283\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:283"}
n
@Aniket Agarwal PTAL ^^
can you share your docker compose file here
a
Hey Ola, Please share the clickhouse configuration, variables passed in the script and clickhouse version you are using
o
docker-compose.yaml
docker-compose.yaml
I just use the default files and configuration as in repo. What clickhouse config are you referring to?
Copy code
docker ps
CONTAINER ID   IMAGE                                        COMMAND                  CREATED        STATUS                  PORTS                                    NAMES
8e0141d08787   signoz/signoz-otel-collector:v0.128.0        "/signoz-otel-collec…"   2 hours ago    Up 2 hours              0.0.0.0:4317-4318->4317-4318/tcp         signoz-otel-collector
0ca2bf994e69   signoz/signoz:v0.88.1                        "./signoz --config=/…"   2 hours ago    Up 2 hours (healthy)    0.0.0.0:8080->8080/tcp                   signoz
4f17607f2ae9   clickhouse/clickhouse-server:24.1.2-alpine   "/entrypoint.sh"         3 months ago   Up 3 months (healthy)   8123/tcp, 9000/tcp, 9009/tcp             signoz-clickhouse
b33fe00f3e69   bitnami/zookeeper:3.7.1                      "/opt/bitnami/script…"   3 months ago   Up 3 months (healthy)   2181/tcp, 2888/tcp, 3888/tcp, 8080/tcp   signoz-zookeeper-1
Please let me know if there is any other information you need from me, thanks.
@Aniket Agarwal Was the provided data I supplied useful or do you need anything else from me?
a
Hey Ola as i can check This is not due to migration this is a clickhouse error, https://github.com/ClickHouse/ClickHouse/issues/60661 One of the workaround for this error is https://github.com/ClickHouse/ClickHouse/issues/66045#issuecomment-2256360306
o
Ok thanks, I will check your links tomorrow.
So from my understanding, people have been successful in solving the issue in two ways, either disabling (setting to 0) allow_simdjson, or by setting cpu in VM to host. I went with the latter to set cpu type to host and it solved my issue. Thanks again for the links.
🙌 1
5 Views
Open in Slack
PreviousNext
Powered by