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, I'D Very Much Like A Feature To Support Clearml Agent Stopping Specified By The Exact Bringup Command: When Trying For Example To Bring Down A Gpu Agent Now, Clearml Brings It Down By The Order In Which The Agents Were Put Up, But Clearml Could Potent

Hi, I'd very much like a feature to support clearml agent stopping specified by the exact bringup command:
when trying for example to bring down a gpu agent now, clearml brings it down by the order in which the agents were put up,
but clearml could potentially infer from the specifications of gpus and queues given which agent I was referring to, and stop the exact one.

Current behavior has caused many times in which I've accidently stopped someone else's agents.

Thanks!

  
  
Posted 2 years ago
Votes Newest

Answers 10


clearml-agent daemon --detached --gpus 0,1,2 --dynamic-gpus --queue 2_gpu_queue=2 --docker --stop

  
  
Posted 2 years ago

I was told not to kill the process, also, finding it on my own seems very un-user-friendly

  
  
Posted 2 years ago

Thanks! I'll wait for the release note/docs update 😁

  
  
Posted 2 years ago

I'm not sure I understand. Can you give a more specific example?

How do you bring down agents currently? I usually kill the process or send tasks.abort via the API

  
  
Posted 2 years ago

Oh sorry:
pip install clearml-agent==1.2.0rc4Also automatically detects if you have an active venv inside the container and uses it instead of the system wide python

  
  
Posted 2 years ago

I'd like if possible a command line, same as I'd just sent, to recognize the specific worker that was brought up in this manner and kill only it

  
  
Posted 2 years ago

ImmensePenguin78
I think the latest RC adds it, should be released later today 🙂

  
  
Posted 2 years ago

ImmensePenguin78 it might be... Let me check, worst case sync after the weekend 🙂
(pypi does contain 1.2.0rc4 and we are finalizing tests so that we can release a stable 1.2.0)

  
  
Posted 2 years ago

AgitatedDove14 , could it be that the GitHub is not synchronized? I can find only up to 1.2.0.rc3 in it.

  
  
Posted 2 years ago

(Following this)

  
  
Posted 2 years ago
1K Views
10 Answers
2 years ago
one year ago
Tags