Hi Team, I am currently facing some issues with Cl...
# general
s
Hi Team, I am currently facing some issues with Clickhouse it is not initialized correctly.
p
HI @surya prakash 👋 This has been resolved in latest release.
s
ok thanks will check
Post upgrade getting this issue
@Prashant Shahi
p
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.
Copy code
kubectl rollout restart -n platform deploy/my-release-signoz-otel-collector deploy/my-release-signoz-otel-collector-metrics
s
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 ● docker.io/busybox:1.35
clickhouse is running properly
but name is changed post upgrade @Prashant Shahi
p
chi-signoz-cluster-0-0-0
this is strange one.
s
inside this clickhouse only running
p
did you override any existing values?
can you share output of this?
Copy code
kubectl get all -n platform
s
no i just used this instructions only
and this too
issue resolved thanks @Prashant Shahi