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

Expose network timeout consumer configs via client profile #712

Merged
merged 1 commit into from
Sep 21, 2021

Conversation

shrijeet-tesla
Copy link
Contributor

This change allows users to set initial connection & RPC response read timeouts
for kafka client. The underlying sarama lib has these two documented as,

DialTimeout  time.Duration // How long to wait for the initial connection.
ReadTimeout  time.Duration // How long to wait for a response.

Through these configs, one could deal with slow responding brokers and avoid
i/o timeouts.

The change also includes minor refactoring to keep the linter happy,
s/time/timestamp to avoid overshadowing from the new 'time' import

This change allows users to set initial connection & RPC response read timeouts
for kafka client. The underlying sarama lib has these two documented as,

```
DialTimeout  time.Duration // How long to wait for the initial connection.
ReadTimeout  time.Duration // How long to wait for a response.
```

Through these configs, one could deal with slow responding brokers and avoid
i/o timeouts.

The change also includes minor refactoring to keep the linter happy,
s/time/timestamp to avoid overshadowing from the new 'time' import
@shrijeet-tesla
Copy link
Contributor Author

I understand this need to be accompanied with a change in the documentation to include these configs. Please let me know the process for that.

@bai bai merged commit 93742b8 into linkedin:master Sep 21, 2021
@bai
Copy link
Collaborator

bai commented Sep 21, 2021

Thanks for contributing! <3

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.

2 participants