Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Hi There

Hi there @<1523701070390366208:profile|CostlyOstrich36> ,
We have two agents, each with its own queue. These agents are running on a Kubernetes cluster, so the Kubernetes scheduler acts as an additional queue by default, as defined in the agent Helm chart.
Recently, we reduced the resources allocated to each agent. After that change, tasks stopped running — any task we enqueue just remains in a pending state.
Even after reverting the pod resource limits back to their original values, the problem continues. No tasks are running, and the queues appear empty with the message "no tasks running," even though tasks are still being enqueued. It looks like nothing is being assigned or started, and the status stays stuck in pending .
image
image

  
  
Posted 4 months ago
Votes Newest

Answers 3


I second what @<1822805241150574592:profile|ShinySparrow39> said 🙂

  
  
Posted 4 months ago

Hi, Are you sure that your workers are connected to the right queue? It looks to me like they are connected to the services and/or default queue. If you click on the worker in the web UI, you can see which queue that particular worker is listening to.

  
  
Posted 4 months ago

Hi Stijn, hi John,
Yes, the worker was connected to the correct queue
The issue turned out to be related to resources. We had to increase the resources for the worker in order for it to start the task, as it wasn't capable of handling it with the previous configuration.
Thanks for pointing it out!

  
  
Posted 4 months ago
577 Views
3 Answers
4 months ago
4 months ago
Tags
Similar posts