Hi All

I'm encountering some issues with the way Elastic agents are launched,
assigned, and terminated. Despite setting the maximum agent count to two,
both agents launch sequentially, with only the first being assigned to the
job.


Here's where it gets tricky: when the staging job completes and triggers
the production job, I expect one of the active agents to take over.
Instead, the production job attempts to launch new agents, fails due to the
max count limit, and runs without any agents, leading to failure.


Additionally, some agent instances remain active for an extended period,
requiring manual termination. This disrupts the workflow significantly.


Has anyone experienced similar issues, or anyone has any suggestions for a
workaround?


Thanks in advance !

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CADKEDRo_0yJjA0y31vOkXzgtVA_MOiSPQEc_uB3fE%3DfguO-wWQ%40mail.gmail.com.

Reply via email to