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
!! In Remote Execution, Do Agents Inherit The Config From The Queue From Which They Pull The Task?

!! In remote execution, do agents inherit the config from the queue from which they pull the task?

  
  
Posted one year ago
Votes Newest

Answers 18


Let me know if you do; would be nice to have control over that 😁

  
  
Posted one year ago

Okay so the only missing thing of the puzzle I think is that it would be nice if this propagates to the autoscaler as well; that then also allows hiding some of the credentials etc 😮

  
  
Posted one year ago

propagates meaning the autoscaler will use it to spin cloud instances?

  
  
Posted one year ago

and I don't think it's in the docs - we'll add that

Very welcome update, please use some highlighting for it too, it's so important for a complete understanding of how the remote execution works

  
  
Posted one year ago

Exactly; the cloud instances (that are run with clearml-agent ) should have that clearml.conf + any changes specified in extra_clearml_configuration for the scaler

  
  
Posted one year ago

Well, that's actually not the current behaviour, and I'm pretty sure we had a good reason for that - I'll try to remember why 🙂

  
  
Posted one year ago

and I don't think it's in the docs - we'll add that

  
  
Posted one year ago

Well, let me check 🙂

  
  
Posted one year ago

Hi UnevenDolphin73 , queues don't have any notion of configuration. Agent running tasks remotely use their own configuration file to execute tasks.

  
  
Posted one year ago

Holy crap this was a light-bulb moment, is this listed somewhere in the docs?
It solves so much of my issues xD

  
  
Posted one year ago

Sorry, I misspoke, yes of course, the agents config file, not the queues

  
  
Posted one year ago

Than yes 😄

  
  
Posted one year ago

Actually SuccessfulKoala55 , there is something like that happening behind the scenes.
I have an AWS Autoscaler running on a services queue, so the autoscaler inherits the configuration used by the services agent, right?
Now, when my autoscaler launched new EC2 instances, they used the same fileserver as the one that was defined in the services agent too 🤔

  
  
Posted one year ago

Hi UnevenDolphin73 , as far as I can remember, the autoscaler does not use its own configuration as the default for the instances it spins up

  
  
Posted one year ago

I guess it does not do so for all settings, but only those that come from Session()

  
  
Posted one year ago

Yeah, obviously it assumes everyone will be talking to the same server 🙂

  
  
Posted one year ago

Right, but that's as defined in the services agent, which is not immediately transparent

  
  
Posted one year ago