aws-lambda-stream icon indicating copy to clipboard operation
aws-lambda-stream copied to clipboard

Published 20 hours ago • verified publisher icon jgilbert01

add-eb-global-support

Open jgilbert01 opened this issue 10 months ago • 2 comments

jgilbert01 avatar Feb 02 '25 02:02 jgilbert01

If we're in the middle of a failover and the publishing is failing, is that considered a retryable error? So in theory it would bypass faulting and retry until the failover is complete and we can continue publishing to the global EB? I think right now its checking based on the smithy error classifications and we use: (isThrottlingError(err) || isTransientError(err) || isServerError(err))

petermyers avatar Feb 04 '25 14:02 petermyers

If we're in the middle of a failover and the publishing is failing, is that considered a retryable error? So in theory it would bypass faulting and retry until the failover is complete and we can continue publishing to the global EB? I think right now its checking based on the smithy error classifications and we use: (isThrottlingError(err) || isTransientError(err) || isServerError(err))

  • right
  • global endpoint is powered by r53 primary/secondary failover
  • our retry feature is not enabled by default for backwards compatibility
  • when enabled the lambda will retry retriable errors, such as 5xx, instead of publishing faults
  • the regional failover will usually take about 5 minutes to avoid premature failover
  • then the events will flow to the secondary region

jgilbert01 avatar Feb 04 '25 16:02 jgilbert01