You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IotHub connection string to Event Hub connection string
IoT Hub Connection String support in Event Hubs
Background:
Azure IotHub instances have built-in Event Hub instances configured for users to publish/consume events from their IotHub devices. The IotHub instance has a connection string that can be used to authenticate the IotHub instance but cannot be used to authenticate Event Hub instance directly as the endpoints are not the same. However, using the IotHub connection string, an Event Hub connection string can be constructed by getting the endpoint from Event Hub service.
History:
In track 1, Event Hub SDK had support for taking an IotHub connection string and internally converting it into Event Hub connection string. So, users had to simply use the IotHub connection string readily available on the portal to access Event Hub.
Current:
For track 2, the feature team decided that Event Hub SDK should not be coupled with IotHub. So, users cannot use IotHub connection string to connect to Event Hub. To fill this void, all languages instead will
Event Hub producer client today requires users to create an EventBatch, tryAdd() events to the batch and send the batch when the user is ready or when the next event does not fit into a batch.
While this API is very helpful to ensure we build a batch that would meet the size restrictions of the AMQP link, it is a cumbersome for cases where the customer is confident that their set of events do actually fit within the size restrictions. There has also been feedback that the client should be smart enough to do batching on its own without having the customer do it.
Options to claim partitions faster in Event Processor
Problem Statement
In track 2 SDK for Event Processor client, the load balancing loop runs at a fixed interval of 10 seconds. When the load is not balanced among active processors, partitions are claimed/stolen one at a time per load balancing loop. This can take a long time for the processors to reach a balanced state. This document contains a few alternate options to speed up the partition-claiming to reach balanced state sooner.
You can jump to the proposed API section if you want to skip all the options considered.
Options
I have listed a few options below and we could potentially combine two or more of them and also make these configurable load balancing strategies.