Skip to content
This repository was archived by the owner on Mar 3, 2023. It is now read-only.

BUG: bookie statefulset helm template specifies incorrect service name #3410

Merged
merged 2 commits into from
Nov 28, 2019

Conversation

the-scott-hand
Copy link
Contributor

The statefulset's service name:
https://github.com/apache/incubator-heron/blob/master/deploy/kubernetes/helm/templates/bookie.yaml#L74
Doesnt match the actual name of the service:
https://github.com/apache/incubator-heron/blob/master/deploy/kubernetes/helm/templates/bookie.yaml#L203
I believe bookie previously was using the podIPs to connect and the service wasnt actually getting used. Changing the useBookieHostNameAsID to true caused the helm chart to use the service for the first time to connect, which ultimately failed since it was named the wrong name.

@the-scott-hand
Copy link
Contributor Author

it might also be worth noting the yaml in general is doing this correctly, and also utilizing the following annotation:

annotations:
service.alpha.kubernetes.io/tolerate-unready-endpoints: "true"

which is the same annotation being utilized by pulsar's bookie:
https://github.com/apache/pulsar/blob/master/deployment/kubernetes/helm/pulsar/values.yaml#L97

@the-scott-hand
Copy link
Contributor Author

added an additional commit to add that annotation

@nwangtw nwangtw merged commit 4bca2e5 into apache:master Nov 28, 2019
sreev pushed a commit to sreev/incubator-heron that referenced this pull request Apr 9, 2020
apache#3410)

* Update bookie template to use correct service name

* helm add bookie toleration for unready endpoints
nicknezis pushed a commit that referenced this pull request Sep 14, 2020
#3410)

* Update bookie template to use correct service name

* helm add bookie toleration for unready endpoints
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants