Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

[incubator/zookeeper] Allow quorumListenOnAllIPs to be configurable #17183

Closed
jlforester opened this issue Sep 17, 2019 · 10 comments
Closed

[incubator/zookeeper] Allow quorumListenOnAllIPs to be configurable #17183

jlforester opened this issue Sep 17, 2019 · 10 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@jlforester
Copy link

Is your feature request related to a problem? Please describe.

When quorumListenOnAllIPs is set to "false" (the default value), Zookeeper binds to only the pod IP address and not 0.0.0.0. This causes problems when using Istio as the proxy sidecar wants to forward packets to the localhost address which is not listening on port 3888, resulting in "connection refused" errors. The end result is that the Zookeeper nodes are unable to elect a leader and the ensemble never starts.

When quorumListenOnAllIPs is set to "true", Zookeeper binds to 0.0.0.0 and the Istio proxy sidecar is able to forward packets to Zookeeper.

Describe the solution you'd like
I would like a new environment value (env.ZK_QUORUM_LISTEN_ALL_IP) added to the values file that would allow quorumListenOnAllIPs to be enabled. The config-script.yaml file would append the directive to the zoo.cfg file. The default value would be "false" to maintain compatibility with previous behavior.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
I've already made and tested this change locally

jlforester added a commit to jlforester/charts that referenced this issue Sep 17, 2019
…elm#17183

* Add env.ZK_QUORUM_LISTEN_ALL_IP to values file
* Append quorumListenOnAllIPs directive to zoo.cfg

Signed-off-by: Jack Forester <[email protected]>
jlforester added a commit to jlforester/charts that referenced this issue Sep 19, 2019
…elm#17183

Remove trailing spaces in values.yaml

Signed-off-by: Jack Forester <[email protected]>
@stale
Copy link

stale bot commented Oct 17, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 17, 2019
@jlforester
Copy link
Author

/remove-lifecycle stale

@stale stale bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 17, 2019
@stale
Copy link

stale bot commented Nov 16, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 16, 2019
@jlforester
Copy link
Author

/remove-lifecycle stale

@stale stale bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 18, 2019
@stale
Copy link

stale bot commented Dec 18, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2019
@jlforester
Copy link
Author

/remove-lifecycle stale

@stale stale bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2019
@stale
Copy link

stale bot commented Jan 17, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 17, 2020
@jlforester
Copy link
Author

/remove-lifecycle stale

@stale stale bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 20, 2020
@stale
Copy link

stale bot commented Feb 19, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 19, 2020
@stale
Copy link

stale bot commented Mar 4, 2020

This issue is being automatically closed due to inactivity.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant