[Bug] Bookie instanceId verification failed

HGHNice commented 2 months ago

Search before asking

[X] I searched in the issues and found nothing similar.

Read release policy

[X] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

Version

image: 3.0.4 k8s deploy

Minimal reproduce step

First, the cluster bookies prompts that it cannot get instance_id and asks me to use bin-bookkeeper shell metaformat to initialize. Then restarting bookies reports this error. I take the instanceId 237fe99b-9a46-4697-bff1-4739d68a9175 is not matching with 52088892-8876-4c1c-b6fa-cf00e487d985 prompt 237fe99b-9a46-4697-bff1-4739d68a9175 to the bookies host to modify the VERSION file. Then restarting it still has the same error, but this time it no longer prompts the instanceId to be modified.

What did you expect to see?

I expect it to start normally

What did you see instead?

org.apache.bookkeeper.bookie.BookieException$InvalidCookieException:

Anything else?

Solution

Are you willing to submit a PR?

[X] I'm willing to submit a PR!

lhotari commented 2 months ago

image: 3.0.4 k8s deploy

@HGHNice Which method is used for the k8s deployment? Is it by Apache Pulsar Helm Chart? Which version of the Helm chart?

HGHNice commented 2 months ago

image: 3.0.4 k8s deploy

@HGHNice Which method is used for the k8s deployment? Is it by Apache Pulsar Helm Chart? Which version of the Helm chart? I'm glad you replied to me. This picture shows the version of helm-chart I use. I would also like to ask how to scale down bookies if I need to.

apache / pulsar