-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[kafka] Expose resolve_canonical_bootstrap_servers_only #26022
Conversation
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pavolloffay @MovieStoreGuy can you take a look as codeowners?
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
@pavolloffay @MovieStoreGuy ping, please let me know of any amendments! |
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
Sarama has since been upgraded automatically in |
@mx-psi Apologies, there is a trivial import error, I'll fix this this evening - unable to at work. |
All sorted @mx-psi |
…ry#26022) **Description:** The latest release of IBM/sarama includes the `resolve_canonical_bootstrap_servers_only` setting for `client.dns.lookup`. In a GSSAPI context, this enables replacing a list of brokers with a single name that resolves to all of the underlying IPs. Previously this would fail with a Kerberos error. This PR exposes the new option in collector config. **Testing:** Added new cases to check the option is set correctly. **Documentation:** Added a description of the parameter to the relevant READMEs.
Description: The latest release of IBM/sarama includes the
resolve_canonical_bootstrap_servers_only
setting forclient.dns.lookup
. In a GSSAPI context, this enables replacing a list of brokers with a single name that resolves to all of the underlying IPs. Previously this would fail with a Kerberos error. This PR exposes the new option in collector config.Testing: Added new cases to check the option is set correctly.
Documentation: Added a description of the parameter to the relevant READMEs.