Pull Queries: Choose correct network interface to advertise for ksql rest api #4151
Comments
vinothchandar
changed the title
big-andy-coates
added a commit
to big-andy-coates/ksql
that referenced
this issue
Dec 18, 2019
Fixes: confluentinc#4142 Fixes: confluentinc#4151 Fixes: confluentinc#4152 Introduces a new `inter.node.listener` that can be used to specify a URL that the node can be contacted on by other nodes. This can be different to the listeners defined in `listeners`. This can be required if `listeners` is set to a wildcard address, i.e. IPv4 `0.0.0.0` or IPv6 `[::]`, or if the node sits behind network infrastructure that requires other nodes to reach it using a different URL. If `inter.node.listener` is not set it still defaults to the first listener in `listener` config. However, it now replaces an wildcard address with `localHost`. This means inter-node comms is still possible for nodes running on the same host. Warnings are logged if the inter-node listener resolves to a loopback or local address.
2 tasks
big-andy-coates
added a commit
that referenced
this issue
Dec 20, 2019
* fix: pull queries should work across nodes Fixes: #4142 Fixes: #4151 Fixes: #4152 Introduces a new `inter.node.listener` that can be used to specify a URL that the node can be contacted on by other nodes. This can be different to the listeners defined in `listeners`. This can be required if `listeners` is set to a wildcard address, i.e. IPv4 `0.0.0.0` or IPv6 `[::]`, or if the node sits behind network infrastructure that requires other nodes to reach it using a different URL. If `inter.node.listener` is not set it still defaults to the first listener in `listener` config. However, it now replaces an wildcard address with `localHost`. This means inter-node comms is still possible for nodes running on the same host. Warnings are logged if the inter-node listener resolves to a loopback or local address.
big-andy-coates
added a commit
to big-andy-coates/ksql
that referenced
this issue
Jan 10, 2020
Backport of confluentinc#4169 Fixes: confluentinc#4142 Fixes: confluentinc#4151 Fixes: confluentinc#4152 Introduces a new `inter.node.listener` that can be used to specify a URL that the node can be contacted on by other nodes. This can be different to the listeners defined in `listeners`. This can be required if `listeners` is set to a wildcard address, i.e. IPv4 `0.0.0.0` or IPv6 `[::]`, or if the node sits behind network infrastructure that requires other nodes to reach it using a different URL. If `inter.node.listener` is not set it still defaults to the first listener in `listener` config. However, it now replaces an wildcard address with `localHost`. This means inter-node comms is still possible for nodes running on the same host. Warnings are logged if the inter-node listener resolves to a loopback or local address. (cherry picked from commit 0ac71cf)
2 tasks
big-andy-coates
added a commit
that referenced
this issue
Jan 26, 2020
Backport of #4169 Fixes: #4142 Fixes: #4151 Fixes: #4152 Introduces a new `inter.node.listener` that can be used to specify a URL that the node can be contacted on by other nodes. This can be different to the listeners defined in `listeners`. This can be required if `listeners` is set to a wildcard address, i.e. IPv4 `0.0.0.0` or IPv6 `[::]`, or if the node sits behind network infrastructure that requires other nodes to reach it using a different URL. If `inter.node.listener` is not set it still defaults to the first listener in `listener` config. However, it now replaces an wildcard address with `localHost`. This means inter-node comms is still possible for nodes running on the same host. Warnings are logged if the inter-node listener resolves to a loopback or local address. (cherry picked from commit 0ac71cf)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The service appears to grab the 0th network interface and broadcasts that. This may not be the one the environment is set up to use to contact between nodes.
The text was updated successfully, but these errors were encountered: