TLDR surya faced issues with Clickhouse not properly initializing. Prashant suggested specific upgrade steps and a pod restart, which successfully resolved the problem.
HI surya :wave: This has been resolved in latest release.
Ref:
ok thanks will check
Post upgrade getting this issue
Prashant
Is clickhouse cluster back up after the upgrade? If yes, this should be resolved in next pod restart. You could try restarting the otel collectors. ```kubectl rollout restart -n platform deploy/my-release-signoz-otel-collector deploy/my-release-signoz-otel-collector-metrics```
i didn't take back up, since i am working in dev environment for testing purpose. While i get the initial issue i reinstalled everything and upgraded signoz as you suggested also now restarted
this is what i am getting from *my-release-signoz-otel-collector-metrics-init ●
clickhouse is running properly
but name is changed post upgrade Prashant
`chi-signoz-cluster-0-0-0` this is strange one.
inside this clickhouse only running
did you override any existing values?
can you share output of this? ```kubectl get all -n platform```
no i just used this
and this
issue resolved thanks Prashant
surya
Fri, 14 Jul 2023 14:24:56 UTCHi Team, I am currently facing some issues with Clickhouse it is not initialized correctly.