Hi WorriedSwan6
On a different issue, have you any solution on how to make the agent listen to multiply queues?
each agent is connected with one type of queue that represents the Job that agent will create. You can connect to it multiple queues, and it will pull from creating the same "type" of job regardless of where it's coming from. If you want another job to be created, just spin another agent, there is no limit to the number of agents you can spin in the cluster (they do not actually require a lot of resources, they sleep most of the time 🙂 )
Is this what you had in mind?
Hey WobblyFrog79 , yes testing this locally it does seems to solve the issue, thank you.
I will test it in our env.
On a different issue, have you any solution on how to make the agent listen to multiply queues?
On the helm it is written :
# -- ClearML queue this agent will consume. Multiple queues can be specified with the following format: queue1,queue2,queue3
But this does not work as the agent will read them all as one queue
This hasn’t worked for me either, I use multiple queues instead. Another reason I also use multiple queues is because I need to specify different resource requirements for pods launched by each queue (CPU-only vs GPU).
Hey Martin, do you know how to connect the agent to multiply queues?
AgitatedDove14 for me it hasn’t worked when I specified agentk8sglue.queue: "queue1,queue2"
in the Helm chart options which should be possible according to documentation. What also hasn’t worked is that flag for creating a queue if it doesn’t exists ( agentk8sglue.createQueueIfNotExists
). Both failed parsing at runtime, so those are 2 bugs I’d say.
hmm, yes it should create the queue if it's missing (btw you could work around that and create it in the UI). Any chance you can open a github issue in the clearml helm chart repo so we do not forget ?