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, Would It Be Possible For The Autoscaler To Support Stopping Instances Instead Of Terminating Them? My Use Case Is The Following: I Am Continuing My Journey With The Clearml-Session Tool, And In Case The Clearml-Session Is Running In A Ec2 Inst

Hi there, would it be possible for the autoscaler to support stopping instances instead of terminating them?

My use case is the following: I am continuing my journey with the clearml-session tool, and in case the clearml-session is running in a ec2 instance, I want to stop the instance and restart it later, so that I don’t loose my progress on my notebooks but I don’t pay for the idle instance. I can do the stopping/restarting manually, but I am thinking it would be very handy if clearml could handle it for me. Of course this would need to be refined to be properly integrated, but in general, would something like that be possible?

EDIT: Maybe this problem can be tackled from a different perspective and be seen as trying to move a clearml-session task state from one agent to another. This allows to terminate an agent when I am done for the day, and continue with another the day after

EDIT 2: For now I can think of a simple solution, which is to centralize my notebooks in a github repo, so that I can simply push my progress at the end of the day and restore it in another agent the day after. This works as far as I don’t have big artifacts living in the instance (that I wouldn’t be able to push to github). I guess this is fine as I can deal with such big artifacts separately (eg. send them to s3)

  
  
Posted one year ago
Votes Newest

Answers


Hi JitteryCoyote63 ,

Regarding Edit 2: This seems like a nice idea.

Regarding adding option to only stop them - Please open a feature request on GitHub 🙂

  
  
Posted one year ago
731 Views
1 Answer
one year ago
one year ago
Tags
Similar posts