Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move bookkeeper metadata initialization to it's own job #145

Open
lhotari opened this issue Jan 31, 2022 · 0 comments
Open

Move bookkeeper metadata initialization to it's own job #145

lhotari opened this issue Jan 31, 2022 · 0 comments

Comments

@lhotari
Copy link
Contributor

lhotari commented Jan 31, 2022

Currently
bookkeeper shell metaformat --nonInteractive is called every time a bookie is started:

# This initContainer will make sure that the bookkeeper
# metadata is in zookeeper
- name: pulsar-bookkeeper-metaformat
image: "{{ .Values.image.bookkeeper.repository }}:{{ .Values.image.bookkeeper.tag }}"
imagePullPolicy: {{ .Values.image.bookkeeper.pullPolicy }}
command: ["sh", "-c"]
args:
- >
bin/apply-config-from-env.py conf/bookkeeper.conf &&
bin/apply-config-from-env.py conf/bkenv.sh &&
bin/bookkeeper shell metaformat --nonInteractive || true;

bookkeeper shell metaformat command is deprecated since 4.7.0
https://bookkeeper.apache.org/docs/latest/reference/cli/#bookkeeper-shell-metaformat

This command is deprecated since 4.7.0, in favor of using initnewcluster for initializing a new cluster and nukeexistingcluster for nuking an existing cluster.

Consider moving the bookkeeper metadata initialization to it's own job

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant