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. If I Understand Right, Dataset And Any Other Task Is Aborted After Some Time Of Inactivity. Can I Configure It On Some Level (Ideally On Task Level)? I Have A Pipeline That Is Expected To Run Several Days.

Hi all. If I understand right, Dataset and any other task is Aborted after some time of inactivity. Can I configure it on some level (ideally on task level)? I have a pipeline that is expected to run several days.

  
  
Posted 2 years ago
Votes Newest

Answers 8


Hi SuccessfulKoala55 Thank you for response. So, it's not possible if we use community server, right?

  
  
Posted 2 years ago

AgitatedDove14 I didn't know about dataset.squish(). Thank you. I'll check this variant today

  
  
Posted 2 years ago

Well, any task that is running using the SDK actually always pings the server in the background

  
  
Posted 2 years ago

So, it's not possible if we use community server, right?

You're right, However I'm not sure this will be an issue for you at all

  
  
Posted 2 years ago

The issue I want to avoid is aborting of the dataset task that these regular tasks update.

HelpfulHare30 could you post a pseudo code of the dataset update ?
(My point is, I'm not sure the Dataset actually supports updating, as it need to reupload the previous delta snapshot). Wouldn't it be easier to add another child dataset and then use dataset.squash (like one would do in git) ?

  
  
Posted 2 years ago

Hi HelpfulHare30 , handling non-responsive tasks termination is done by a server watchdog, which can be configured using server settings. See https://clear.ml/docs/latest/docs/deploying_clearml/clearml_server_config#non-responsive-task-watchdog for more details. Since the documentation there is a bit lacking, I'll just point out you can also disable it completely using the services.tasks.non_responsive_tasks_watchdog.enabled: false setting.

  
  
Posted 2 years ago

SuccessfulKoala55 , I have the following structure now (maybe it's not best practice and you can suggest a better one). There is a sequence of tasks, that are run manually or from pipeline. Every task at the end updates some dataset. The dataset should be closed only after all the sequence is finished (and some task in the sequence can take more than two days). The issue I want to avoid is aborting of the dataset task that these regular tasks update.

  
  
Posted 2 years ago

Do I understand right that I can avoid task (including dataset termination if I update it somehow once a period (say, sending a log line)?

  
  
Posted 2 years ago
586 Views
8 Answers
2 years ago
one year ago
Tags