Can I scale an (1.0) agent to 3x replicas with the same service account / api key? Or does each replica need its own service account and api key?
โ 1
k
Kevin Kho
06/13/2022, 5:47 PM
They can use the same API key, but there is no load balancing. Itโs more like there are 3 processes that poll at 10 second intervals and then whatever agent picks up the flow gets it. If itโs unable to start, Lazarus may re-submit it and then run it. Are the 3 agents on different compute?
๐ 1
Kevin Kho
06/13/2022, 5:47 PM
What kind of agent is this?
b
Brian Phillips
06/13/2022, 5:48 PM
ECS Agent in an ECS Service with 3 replicas
Brian Phillips
06/13/2022, 5:49 PM
With different service accounts would prefect cloud load balance across compatible agents, or is it still the first agent to poll gets the flow?
k
Kevin Kho
06/13/2022, 5:51 PM
Still the first to poll it. A bit confused why ECS would need multiple replicas though since the execution is Serverless?
b
Brian Phillips
06/13/2022, 5:52 PM
We've seen a single agent start to queue up scheduled flows with 1,000+ concurrent flows
k
Kevin Kho
06/13/2022, 5:56 PM
Oh wow. Are you able to run all those if you have 3 agents? You could maybe split up the label?
b
Brian Phillips
06/13/2022, 6:00 PM
I'm not sure ๐ just exploring how we can handle large numbers of concurrent flows right now. I only saw a single agent in the UI after I scaled to 3 replicas so wanted to check that I was actually getting additional agent bandwidth. It sounds like the answer is yes, but there is no differentiating which replica a flow landed on in the UI.
๐ฏ 1
k
Kevin Kho
06/13/2022, 6:09 PM
You do, but it just appears as one so that if you stop an agent and restart it, it will appear as the same in the UI
Kevin Kho
06/13/2022, 6:09 PM
So the UI treats it as the same entity but you really have three going on under the hood