No response from server sometimes

[ashwin-nath-m]

Describe the bug When creating a room with compositeegress, sometimes an error is thrown no response from servers.

Egress Version v1.8

Logs

The logs from livekit container is

2024-07-30T08:55:55.049Z        WARN    livekit.psrpc.EgressInternal.StartEgress        rpc/logging.go:66       client error    {"topic": [""], "request": {"egressId": "EG_cbjYwoQ48rif", "roomComposite": {"roomName": "dev_9105", "layout": "grid", "file": {"fileType": 1, "filepath": "seller/recordings/51/recording_66a8aa84a0b73.mp4", "s3": {"accessKey": "key32424", "secret": "sad34", "region": "ap-south-1.linodeobjects.com", "endpoint": "https://ap-south-1.linodeobjects.com", "bucket": "store.brand.to"}}, "fileOutputs": [{"fileType": 1, "filepath": "seller/recordings/51/recording_66a8aa84a0b73.mp4", "s3": {"accessKey": "dada3", "secret": "erwfrf3", "region": "ap-south-1.linodeobjects.com", "endpoint": "https://ap-south-1.aasd.com", "bucket": "store.brand.to"}}]}, "roomId": "RM_HC3FjcYYvjBi"}, "response": null, "duration": "22.393122289s", "error": "no response from servers"}
2024-07-30T08:55:55.049Z        INFO    livekit.api     service/twirp.go:124    API Egress.StartRoomCompositeEgress     {"service": "Egress", "method": "StartRoomCompositeEgress", "room": "brand_dev_9105", "baseUrl": "", "outputType": "file", "duration": "22.393481626s", "status": "503", "error": "no response from servers", "code": "unavailable"}
2024-07-30T08:56:39.567Z        INFO    livekit service/roomallocator.go:148    selected node for room  {"room": "brand_dev_9106", "roomID": "RM_dzt2sampCjiA", "selectedNodeID": "ND_231asVWMFxn"}

egress yaml configuration is

redis:
    address: localhost:6379
    username: ""
    password: ""
    db: 0
    use_tls: false
    sentinel_master_name: ""
    sentinel_username: ""
    sentinel_password: ""
    sentinel_addresses: []
    cluster_addresses: []
    max_redirects: null
api_key: API90ndksd
api_secret: KEY239032e
ws_url: wss://signal.brand.com

However i dont see any logs in egress container around same timestamp though

2024-07-30T08:54:17.194Z        INFO    egress  server/server_rpc.go:55 request received        {"nodeID": "NE_f8fX36sHiwG9", "clusterID": "", "egressID": "EG_CkStocPywyQx"}
2024-07-30T08:54:17.196Z        INFO    egress  server/server_rpc.go:72 request validated       {"nodeID": "NE_f8fX36sHiwG9", "clusterID": "", "egressID": "EG_CkStocPywyQx", "requestType": "room_composite", "outputType": "file", "room": "brand_dev_9104", "request": {"RoomComposite":{"room_name":"brand_dev_9104","layout":"grid","Output":{"File":{"file_type":1,"filepath":"seller/recordings/51/recording_66a8aa3897ab1.mp4","Output":{"S3":{"access_key":"{access_key}","secret":"{secret}","region":"ap-south-1.linodeobjects.com","endpoint":"https://ap-south-1.linodeobjects.com","bucket":"store.brand.to"}}}},"Options":null,"file_outputs":[{"file_type":1,"filepath":"seller/recordings/51/recording_66a8aa3897ab1.mp4","Output":{"S3":{"access_key":"{access_key}","secret":"{secret}","region":"ap-south-1.linodeobjects.com","endpoint":"https://ap-south-1.linodeobjects.com","bucket":"store.brand.to"}}}]}}}
2024-07-30T08:54:17.213Z        INFO    egress  redis/redis.go:142      connecting to redis     {"nodeID": "NE_f8fX36sHiwG9", "handlerID": "EGH_DK75imEij8VX", "clusterID": "", "egressID": "EG_CkStocPywyQx", "simple": true, "addr": "localhost:6379"}
2024-07-30T08:59:16.830Z        INFO    egress  source/web.go:286       chrome: END_RECORDING   {"nodeID": "NE_f8fX36sHiwG9", "handlerID": "EGH_DK75imEij8VX", "clusterID": "", "egressID": "EG_CkStocPywyQx"}
2024-07-30T08:59:16.894Z        INFO    egress  service/io.go:75        egress updated  {"nodeID": "NE_f8fX36sHiwG9", "clusterID": "", "egressID": "EG_CkStocPywyQx", "requestType": "room_composite", "outputType": "file", "status": "EGRESS_ABORTED"}

What could be the issue?