Missed your message there @<1544853721739956224:profile|QuizzicalFox36> - I've been receiving the same warning with the docker flag provided too unfortunately.
@<1523701087100473344:profile|SuccessfulKoala55> , that's a shame but thank you for the clarification. I'm not sure how much on an option the scale/enterprise tiers are for us right now so it sounds like we'll need to re-think this a little bit. Just to double check - there's no other way of us limiting the number of workers on a daemon in services mode with a self-hosted server?
I am no expert but from your example it seems that you aren't running in docker mode. Or is it just an example? services-mode is supported on docker mode only
Hi @<1523701087100473344:profile|SuccessfulKoala55> , we're using the pre-built EC2 AMI I believe. We did an update on this a few weeks back so hopefully still up to date! Here's the version info from the app:
WebApp: 1.9.2-317 • Server: 1.9.2-317 • API: 2.23
I noticed that workers.set_runtime_properties
isn't in the API reference either?
@<1534706830800850944:profile|ZealousCoyote89> are you using a locally hosted server? If so, what's the server's version?
Hi @<1534706830800850944:profile|ZealousCoyote89> , this is a feature supported only in the scale and enterprise versions of ClearML (requires server-side support)
@<1534706830800850944:profile|ZealousCoyote89> that's correct. You can of course spin up several agents (not in services more, probably with the --cpu-only
flag) to service the same queue, each capable of servicing a single task.