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

Add timeouts for cluster metadata initialization and for init containers #218

Merged
merged 1 commit into from
Jun 20, 2024

Conversation

lhotari
Copy link
Member

@lhotari lhotari commented Jan 27, 2022

Motivation

  • Sometimes the Pulsar deployment doesn't complete, and the broker services don't become available. When investigating the problem, it seems that cluster metadata initialization might get stuck and that blocks starting the pods.
  • This problem seems to happen with Pulsar 2.8.x+ and Zookeeper, when TLS is enabled for Zookeeper. Bump to Pulsar 2.8.2 #190 is the PR to switch to use Pulsar 2.8.x .

Modifications

  • Add timeouts for waiting for zk and bk to become available.
    • timeouts will help failures recover eventually
  • Add timeout to cluster metadata initialization jobs

- Add timeouts for waiting for zk and bk to become available.
- If the waiting gets stuck for some reason, the Pulsar deployment never
  becomes starts the broker services.
  - timeouts will help failures recover eventually
@lhotari lhotari force-pushed the lh-add-metadata-init-timeouts branch from f2296ac to 0e2de35 Compare June 19, 2024 13:41
@lhotari lhotari merged commit 70f36ff into apache:master Jun 20, 2024
30 checks passed
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

Successfully merging this pull request may close these issues.

1 participant