Egress upload retry policy

Egress / Ingress
,
1

Hi,

I’m wondering if there is any retry policy implemented in LiveKit Cloud hosted Egress. There was an error with uploading recording to our GCP bucket due to connection lost. Can we expect it to be retired or recording is lost?

EgressId: EG_mEyjhemhe5AE

SessionId: RM_uBbC8RSrWiQo

2

Hey @Marek_Adamkiewicz - Livekit Cloud hosted egress does have built in retries. Specifically for GCP, every upload is configured with: storage/gcp.go at main · livekit/storage · GitHub

  storage.WithBackoff(gax.Backoff{                                                                        
      Initial:    100ms,                                                                                  
      Max:        5s,                                                                                   
      Multiplier: 2,                                                                                      
  })

So each individual upload to GCP will retry up to 5 attempts with exponential backoff (100ms → 200ms → 400ms → 800ms → 1.6s, capped at 5s).

Additionally there is an option to configure backup storage so that if the primary upload fails, egress tries to upload there instead. In that case the recording is only lost if both primary and backup storage uploads fail.