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

[Event Hubs Client] Processor Stop - Aborts Links #21242

Merged
merged 1 commit into from
May 21, 2021

Conversation

jsquire
Copy link
Member

@jsquire jsquire commented May 20, 2021

Summary

The focus of these changes is to detect that an event processor is attempting to stop and force-close the AMQP links being used to read events. This should help to avoid pauses when stopping due to an active AMQP operation in the transport consumer being blocked waiting for its timeout because no events were available.

References and Related

@jsquire jsquire added Event Hubs Client This issue points to a problem in the data-plane of the library. labels May 20, 2021
@jsquire jsquire added this to the [2021] June milestone May 20, 2021
@jsquire jsquire self-assigned this May 20, 2021
@jsquire jsquire force-pushed the eventhubs/processor-cancel branch from d7cb633 to def1208 Compare May 20, 2021 21:16
@jsquire
Copy link
Member Author

jsquire commented May 20, 2021

/azp run net - eventhub - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@Azure Azure deleted a comment from azure-pipelines bot May 20, 2021
@Azure Azure deleted a comment from azure-pipelines bot May 20, 2021
@jsquire
Copy link
Member Author

jsquire commented May 20, 2021

//cc: @danielmarbach

@jsquire jsquire changed the title [Event Hubs Client] Processor Stop Aborts Links [Event Hubs Client] Processor Stop - Aborts Links May 20, 2021
@jsquire jsquire force-pushed the eventhubs/processor-cancel branch from def1208 to 20da85a Compare May 21, 2021 16:17
@jsquire
Copy link
Member Author

jsquire commented May 21, 2021

/azp run net - eventhub - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

The focus of these changes is to detect that an event processor is attempting
to stop and force-close the AMQP links being used to read events.  This
should help to avoid pauses when stopping due to an active AMQP operation
in the transport consumer being blocked because no events were available.
@jsquire jsquire force-pushed the eventhubs/processor-cancel branch from 20da85a to 2b179cf Compare May 21, 2021 19:25
@jsquire
Copy link
Member Author

jsquire commented May 21, 2021

/azp run net - eventhub - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@danielmarbach
Copy link
Contributor

LGTM

@jsquire
Copy link
Member Author

jsquire commented May 21, 2021

/check-enforcer evaluate

@jsquire jsquire merged commit 27db304 into Azure:master May 21, 2021
@jsquire jsquire deleted the eventhubs/processor-cancel branch May 21, 2021 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants