https://signoz.io logo
Join Slack
Powered by
I just tried to upgrade my self-hosted signoz inst...
# support
o
I just tried to upgrade my self-hosted signoz instance from 0.47 to 0.53 but it failed migration 😞 I then saw that there was an instruction in docs to run some commands when upgrading to 0.51 if coming from pre 0.49 release. I tried those commands but couldn't get the alter command to run after entering clickhouse by running clickhouse client. As a hail mary I tried to checkout 0.49 instead and run the install command but migration failed there as well. I'm now afraid that I have borked the entire deployment 😢 A bit of a noob when it comes to docker I should add. Any help appreciated
I was able to execute the commands to change index by removing 
ON CLUSTER {{.SIGNOZ_CLUSTER}}
part from the command. But migration container still fail to run.
docker logs from otel-migrator show 
Dirty database version 14. Fix and force version.
I managed to find some old thread that suggested to run 
DROP TABLE signoz_logs.schema_migrations
so I did that and after this I could run install.sh and have everything start. Can I be sure that all migrations from 0.47 to 0.53 executed correctly? or should I run some migrations manually now after?
Ok, so I checked all migration scripts from https://github.com/SigNoz/signoz-otel-collector/tree/main/migrationmanager/migrators/logs/migrations 000010 => and all changes in those seem to have been applied. After deleting 
signoz_logs.schema_migrations
and re-running install script, all services started and I can access signoz again. If I enter clickhouse and check content of this table again I can see this. Is this the expected result I should see?
Copy code
clickhouse :) select * from signoz_logs.schema_migrations

SELECT *
FROM signoz_logs.schema_migrations

Query id: 70e369c7-b71d-44aa-984b-eedbbee067dc

┌─version─┬─dirty─┬────────────sequence─┐
│       1 │     1 │ 1725007515445448027 │
│       1 │     0 │ 1725007515845067837 │
│       2 │     1 │ 1725007515847659310 │
│       2 │     0 │ 1725007515905199014 │
│       3 │     1 │ 1725007515906956452 │
│       3 │     0 │ 1725007516074890985 │
│       4 │     1 │ 1725007516076887155 │
│       4 │     0 │ 1725007516133613526 │
│       5 │     1 │ 1725007516135661125 │
│       5 │     0 │ 1725007516691938663 │
│       6 │     1 │ 1725007516694060263 │
│       6 │     0 │ 1725007516808924862 │
│       7 │     1 │ 1725007516810876771 │
│       7 │     0 │ 1725007516978563302 │
│       8 │     1 │ 1725007516980545922 │
│       8 │     0 │ 1725007517259336785 │
│       9 │     1 │ 1725007517261254373 │
│       9 │     0 │ 1725007517373976862 │
│      10 │     1 │ 1725007517376240733 │
│      10 │     0 │ 1725007517378942645 │
│      11 │     1 │ 1725007517380362852 │
│      11 │     0 │ 1725007517986887170 │
│      12 │     1 │ 1725007517988498798 │
│      12 │     0 │ 1725007517990213317 │
│      13 │     1 │ 1725007517991286101 │
│      13 │     0 │ 1725007517992838018 │
└─────────┴───────┴─────────────────────┘
┌─version─┬─dirty─┬────────────sequence─┐
│      14 │     0 │ 1725007518704759579 │
└─────────┴───────┴─────────────────────┘
┌─version─┬─dirty─┬────────────sequence─┐
│      14 │     1 │ 1725007517993915233 │
└─────────┴───────┴─────────────────────┘

28 rows in set. Elapsed: 0.002 sec.
s
Yes, this is expected
We are working on improving the migration experience.
23 Views
Open in Slack
PreviousNext
Powered by