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 All, I Am Having An Issue With Clearml Scheduler Where It Doesn'T Reuse The Task As I Would Expected. I Have Raised

Hi all, I am having an issue with ClearML Scheduler where it doesn't reuse the task as I would expected. I have raised this issue . Has anyone else experienced this?

  
  
Posted 9 months ago
Votes Newest

Answers 10


Hi @<1529271085315395584:profile|AmusedCat74>

ClearML Scheduler where it doesn't reuse the task

What do you mean by doesn't reuse the Task, do you mean you want each time the scheduler is launched to basically overwrite the previous run ?

  
  
Posted 9 months ago

I don't want a new task every 5 minutes as that will create a lot of tasks over a day. It would be better if I had just one task.

Oh you mean the Task that will be launched will override the previous "instance", correct ?

  
  
Posted 9 months ago

Yep that's correct. If I have a task which runs every 5 minutes, I don't want a new task every 5 minutes as that will create a lot of tasks over a day. It would be better if I had just one task.

  
  
Posted 9 months ago

This is not working. Please see None which details the problem

  
  
Posted 9 months ago

And you pass:

scheduler.add_task(..., reuse_task=True)

?

  
  
Posted 9 months ago

Yep 👍

  
  
Posted 9 months ago

Oh I see your point, that makes sense, it should check the state of the Task and force it to aborted so it can be renequed, the issue with reset it will clear the previous run execution, which I think we do not want, Wdyt?

  
  
Posted 9 months ago

If a Task is in the 'Completed' I think the only option is to 'Reset' it (see image). You do clear the previous run execution but I think for a repetitive task this is fine.
Maybe this should only be the case if it is in a 'Completed' state rather than 'Failed'. I can see that in this case you would not want to clear the execution because you would want to see why it Failed. Thoughts?
image

  
  
Posted 9 months ago

If a Task is in the 'Completed' I think the only option is to 'Reset' it (see image).

In the UI yes, in code you can do task.mark_aborted(force=True)

You do clear the previous run execution but I think for a repetitive task this is fine.

I would avoid that, no?

  
  
Posted 9 months ago

Ah, didn’t know that. Yes in that case that would work 👍

  
  
Posted 9 months ago
573 Views
10 Answers
9 months ago
9 months ago
Tags