This message was deleted.

we had improved this capability here. It's capable of handling multiple concurrent Egresses now. We gotta update the docs 🙂

Sounds cool 🙂 What is the logic when assigning a Room Composite request to an egress? or can we disable this option? We are scaling egress instances by number of active rooms. I would want to spread this Room Composites requests to different instances when available.

hmm I don't think we currently support that

I might misexplained myself. I want to keep using old behavior. One room composite recording per egress instance

I see, you can achieve that by configuring the resource cost for room composites. in the config, ensure that the cpu count in the config matches your pod config

cpu_cost: # optionally override cpu cost estimation, used when accepting or denying requests
  room_composite_cpu_cost: 3.0

Thanks! 🙂

can you attach logs from when Egress started?

Sounds like we have a bug with CPU requirements. If you're running on 4 CPU with the requirement set to 4.5, it shouldn't accept even one

Do you want me to open a GitHub issue?

If you want to keep track of it, you can open one and I'll post updates there. Otherwise, you can expect a fix in the next egress release

Thank you guys! 🙂