Reqs to the api

Ok thanks, I’m searching a way to not be dependent on the aws auto scaler script but rather use a k8s job which will run and die after it’s finished thus saving resources

Returned 400 for users.get_current_user in 3ms, msg=Invalid user (failed loading user)

maybe change the session cookie to 24 hours?

Yes that would be awesome

Hey I have another question:
How to I use gunicorn in api server?
I see that during the build in the entrypoint.sh you have an env called “CLEARML_USE_GUNICORN”
How do I use it in the helm charts or do I need to build a custom image?

sure

users.get_preferences
users.get_current_user
Post reqs fail…

cloned the repo “clearml-helm-charts”

I had an old cookie from an old deployment that’s why it didn’t recognize my user…

Some way more k8s native like a job with a base image and the exported task

simple helm install, didn’t change anything in values

I see some keys from apiserver that are a couple of hundreds of mb

Also added the “CLEARML_SUPPRESS_UPDATE_MESSAGE” env which didn’t work…

Helm charts

🙏 Thanks guys!

Thanks! SuccessfulKoala55 I’ll take a look

The cookie has a ttl of 3000+ years…

With

I’ll test without parentheses

When running with --local True
everything works btw… but locally 🙃

You think it’s the “--services-mode” flag?

oooo

Thanks a lot!

One of the keys:
b”<class ‘apiserver.database.model.base.GetMixin.GetManyScrollState’>/f4010ba7df0f45dbbea10a71fe568a94"

SuccessfulKoala55 Seems like apiserver uses redis as cache for ui pagination with a long ttl

Sure no problem thanks!

Maybe this?
It’s the entrypoint file for the docker

One moment

I only enabled the pod and created services queue