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
My team is working on a scheduler component which basically goes through the payload intake and distribute the load across all event hubs determined by the region (Payload will have an array of items that have a region as a field).
I want to be able to say if sending the batch of events have failed due to resource being down or bad name, I want to send it a different one (round robin for the sake of POC). I thought about using the azure resource health api, but I want to minimize the REST calls as much as possible as it's quite expensive. I've written a test with a random namespace that doesn't exist and instead of returning an exception/error, it panicked and exited my program. Is it possible to have a graceful method for this so I can have a handler that will apply round robin algorithm if there was an exception/error from .SendBatch()?
The text was updated successfully, but these errors were encountered:
So I have a quick question.
My team is working on a scheduler component which basically goes through the payload intake and distribute the load across all event hubs determined by the region (Payload will have an array of items that have a region as a field).
I want to be able to say if sending the batch of events have failed due to resource being down or bad name, I want to send it a different one (round robin for the sake of POC). I thought about using the azure resource health api, but I want to minimize the REST calls as much as possible as it's quite expensive. I've written a test with a random namespace that doesn't exist and instead of returning an exception/error, it panicked and exited my program. Is it possible to have a graceful method for this so I can have a handler that will apply round robin algorithm if there was an exception/error from .SendBatch()?
The text was updated successfully, but these errors were encountered: