github Azure/azure-sdk-for-net Azure.Messaging.EventHubs.Processor_5.2.0

latest releases: Microsoft.Azure.WebJobs.Extensions.AuthenticationEvents_1.0.0-beta.8, Azure.AI.OpenAI.Assistants_1.0.0-beta.4, Azure.Communication.CallAutomation_1.2.0...
3 years ago

5.2.0 (2020-09-08)

Acknowledgments

Thank you to our developer community members who helped to make the Event Hubs client libraries better with their contributions to this release:

Changes

Key Bug Fixes

  • The approach used for creation of checkpoints has been updated to interact with Azure Blob storage more efficiently. This will yield major performance improvements when soft delete was enabled and minor improvements otherwise.

  • The EventProcessorClient will now perform an eager validation of connection strings upon creation. Previously, validation was deferred until a partition was claimed which made debugging difficult.

  • Fixed an issue where failure to create an AMQP link would lead to an AMQP session not being explicitly closed, causing connections to the Event Hubs service to remain open until a garbage collection pass was performed.

New Features

  • Load balancing will now detect when it has reached a balanced state more accurately; this will allow it to operate more efficiently when LoadBalancingStrategy.Greedy is in use.

  • The EventProcessorClient now supports a configurable strategy for load balancing, allowing control over whether it claims ownership of partitions in a balanced manner (default) or more aggressively. The strategy may be set in the EventProcessorClientOptions when creating the processor. More details about strategies can be found in the associated documentation.

  • The EventProcessorClientOptions now support setting a PrefetchCount and CacheEventCount for performance tuning. More details about each can be found in the associated documentation.

  • Connection strings for each of the clients now supports a SharedAccessSignature token, allowing a pre-generated SAS to be used for authorization.

  • Load balancing now has better recognition for being in a recovery state and will aggressively reclaim partitions for which it is the recognized owner, regardless of whether the current instance made the ownership claim. Previously, those partitions were redistributed on a 1-by-1 basis as part of the standard cycle.

Don't miss a new azure-sdk-for-net release

NewReleases is sending notifications on new releases.