-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[EventHubs] Add keep_alive_interval to producer client #23361
Conversation
API changes have been detected in API changes + keep_alive_interval: Union[int, None] = ...,
+ keep_alive_interval: Union[int, None] = ...,
+ keep_alive_interval: Union[int, None] = ...,
+ keep_alive_interval: Union[int, None] = ..., |
Could you potentially extend this to cover comsumer client as well? |
hey @98christianp, may I ask why would you like the support for EventHubConsumerClient? The EventHubConsumerClient is supposed to be running forever which should not encounter the issue. |
Thanks for your reply @yunhaoling
This puts my process into a permenant loop where it tries to connect and ends with "Cannot get source or target. Detaching link" |
Hi @yunhaoling. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days. |
Hi @yunhaoling. Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing "/reopen" if you'd like to continue working on these changes. Please be sure to use the command to reopen or remove the "no-recent-activity" label; otherwise, this is likely to be closed again with the next cleanup pass. |
Expose keep alive config on producer client
potentially addressing issue: #21849
two issues:
keep_alive_interval
secondsIt is still unclear why the execution hangs after connection closed
addressing issue 1 might help the end to end scenario, however, azure function's behavior is unclear -- whether it's stateful or stateless: