Creating a bookkeeper cluster block in initialization.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
Research direction
Locate the Helm template that creates the pulsar-bookie-init job and inspect the metadataPrefix branch invoking ZooKeeperMain. Reproduce it with the provided values and verify why initialization remains running; done means the job completes normally while metadataPrefix remains set.
Written by the indexing model from the issue text.
Description
I use helm to install a bookkeeper cluster and set up a metadataPrefix by default value "/configuration-store".
My config file
metadataPrefix: "/configuration-store"
components:
# zookeeper
zookeeper: true
# bookkeeper
bookkeeper: true
# bookkeeper - autorecovery
autorecovery: true
# broker
broker: false
# proxy
proxy: false
# toolset
toolset: false
# pulsar manager
pulsar_manager: false
monitoring:
# monitoring - prometheus
prometheus: false
# monitoring - grafana
grafana: false
I find that pulsar-bookie-init job still running but not terminate, I found it was blocking in the process that command below
{{- if not (eq .Values.metadataPrefix "") }}
bin/bookkeeper org.apache.zookeeper.ZooKeeperMain -server {{ template "pulsar.fullname" . }}-{{ .Values.zookeeper.component }} create {{ .Values.metadataPrefix }} 'created for pulsar cluster "{{ template "pulsar.fullname" . }}"' || yes &&
{{- end }}
When I replace the metadataPrefix value to "" and the job skip that process and completed normally.
I can't certain whether it is a bug or I need some extra configuration.
- Dominant language
- Go Template
- Stars
- 81
- Forks
- 69
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from streamnative/charts
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
streamnative/charts#1213 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
streamnative/charts#1146 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
streamnative/charts#1138 ·
-
[pulsar-operator] how to set different kafkaAdvertisedListeners for different pulsar broker podOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
streamnative/charts#1107 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
streamnative/charts#1057 ·
All issues in streamnative/charts
Similar issues
-
area:ai-suggestions bug P1
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
uttrflow/uttrflow-swift#3456 ·
Maintainers usually reply within 1 day
-
easy low
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
open-nudge/opentemplate#185 ·
Maintainers usually reply within 1 day
-
good-first-issue help-wanted security-slam
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
agent/quality hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cncf/endusers#972 · 1 comment ·
Maintainers usually reply within 1 day
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
IBM/ansible-lifecycle-driver#297 ·