ZGaetano
b27b9f6909
Root cause of stuck 'processing', failed deletes, and dead playback: The mam-api proxies media (/video, /hls pipe the full S3 body through Express), holding long-lived streaming sockets. With the SDK's default http agents (no keep-alive, unbounded but unpooled) those streams starved control-plane calls — DeleteObject and the proxy worker's master download — which timed out (10s connectionTimeout) in bursts. Fixes: - mam-api S3 client: dedicated keep-alive http/https Agents (maxSockets 256) + requestTimeout raised 30s→300s so large master GETs finish. - worker S3 client: previously had NO handler config at all (SDK defaults). Added keep-alive agents + 600s requestTimeout so proxy/conform master downloads (hundreds of MB) don't stall and leave assets in 'processing'. |
||
|---|---|---|
| .. | ||
| src | ||
| test | ||
| .env.example | ||
| .gitignore | ||
| Dockerfile | ||
| package-lock.json | ||
| package.json | ||