@<1729671499981262848:profile|CooperativeKitten94> thanks that indeed helped!!
same helped for elastic db (its important to scale back to 1 and not to 3 right after data migration).
finally im done, thanks for helping 🙂

thanks @<1523701070390366208:profile|CostlyOstrich36> , the big challenge is the versions of the databases in the docker compose and the versions in the sub charts of mongo and elastic in the helm chart im using. in the helm chart mongo is in version 5 and the newest docker compose still using mongo4.4 and while trying to migrate data from mongo4.4 to mongo 5 its got broken. while trying to change the mongo version in the chart to 4.4 its still got broken. so im kinda lost at the moment, im...

hi @<1734020208089108480:profile|WickedHare16> what was the issue here with the api server? im getting the same warning log:

[2024-08-18 14:03:26,881] [9] [WARNING] [clearml.service_repo] Returned 400 for  in 0ms, msg=Invalid request path /

not sure why

yes, less than 1 minute

thanks i meant debug.ping and its indeed working!

@<1729671499981262848:profile|CooperativeKitten94> the pod is crashing during the migration of the files, im copying the db folder with all the wt files, etc. into the db folder of the mongo pods