Question:
What Happens When a Streaming Event is Unsuccessful?
If their Azure topic is unreachable for any particular reason (throttling, network issues, cloud outage, etc.), what will happen to the Reltio events that have failed to send.
Answer:
Please see Microsoft Documentation on Service Bus retries:
https://learn.microsoft.com/en-us/azure/architecture/best-practices/retry-service-specific#service-bus
Retry usage guidance
The ServiceBusRetryOptions property specifies the retry options for the ServiceBusClient object:
Expand table
| Setting | Default value | Meaning |
|---|---|---|
| CustomRetryPolicy | A custom retry policy to be used in place of the individual option values. | |
| Delay | 0.8 seconds | The delay between retry attempts for a fixed approach or the delay on which to base calculations for a backoff-based approach. |
| MaxDelay | 60 seconds | The maximum permissible delay between retry attempts. |
| MaxRetries | 3 | The maximum number of retry attempts before considering the associated operation to have failed. |
| Mode | Exponential | The approach to use for calculating retry delays. |
| TryTimeout | 60 seconds | The maximum duration to wait for completion of a single attempt, whether the initial attempt or a retry. |
I believe Reltio uses the default settings.
I believe it's similar to AWS SQS in which it runs the failed messages automatically and has a set dead-event timer in which the messages will then be sent to a Dead-letter-queue to prevent failed messages from being expunged from the queue (this prevents data loss).
Please see how message workflows are in Reltio:
https://docs.reltio.com/en/explore/get-going-with-apis-and-rocs-utilities/reltio-rest-apis/integrate-apis/events-api/message-streaming
References:
https://reltio.zendesk.com/agent/tickets/110500
Comments
Please sign in to leave a comment.