On Thu, Apr 25, 2024 at 10:01 PM Satya Elipe <satya.el...@gmail.com> wrote:
> 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. > Do you want the job to run on both the agents? If so, then these instructions will help you: https://docs.gocd.org/current/advanced_usage/admin_spawn_multiple_jobs.html > > 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. > > > Do the various jobs have an elastic profile ID set? What is the error that you see due to the max count limit? When you say "staging job", do you have a stage in a pipeline called "staging" with one job in it? Or do you have a stage in a pipeline with one job called "staging" and the other called "prod"? Could you share how your pipelines are composed? I'm especially asking this since many new users tend to use GoCD after using other tools and carry over some of the terminology but also the constraints. If you share your pipeline structure and what you want to achieve, then we can design something together. > Additionally, some agent instances remain active for an extended period, > requiring manual termination. This disrupts the workflow significantly. > > > On our cluster, we see the pods being activated upon need, then the relevant job runs in the pod, and the pod is then deactivated. We are sticking to the default of "10 pods" right now, and will be increasing the limit after certain parallel-load reviews. Could you share your Cluster Profile and the Elastic Profile? Please take care to obfuscate any org-specific information such as IP addresses, hostnames, AWS ARNs, URLs, etc. > 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 > <https://groups.google.com/d/msgid/go-cd/CADKEDRo_0yJjA0y31vOkXzgtVA_MOiSPQEc_uB3fE%3DfguO-wWQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CANiY96Yvww_OoK3tzZ%3DogcDjN82FGfydkOoFvxxpCDwHRzKV9A%40mail.gmail.com.
