But without navigation bar, it's quiet inconvenient 😢 ...Do you known why? SuccessfulKoala55

AppetizingMouse58 here:

GrumpyPenguin23
It seems the solution 3 is the fastest way, and i can reuse my code easily. It works now~ That's quite interesting, but the learning curve seems a bit steep for me.Do you have any material or suggestion for learning that?

Thanks for your reply!

I know why, because i used the old apiserver.conf, i set fixed_users. After log in http://xxx:8080/login , it's ok now

Hi SuccessfulKoala55 I find why the ES version is not upgraded to 7.16, because the script provided here is 7.6 https://clear.ml/docs/latest/docs/deploying_clearml/clearml_server_es7_migration

OK i will try again, this time i won't upgrade ES, But do increase vm.max_map_count and open access of /opt/clearm. Why i do again is i found the web ui is fine in deployed machine, but it's weird in my local machine:

Hi GrumpyPenguin23 ,
Thanks your reply.
In 2, dose that mean i should develop another tool to parse the json standalone? 3 is a good solutionAnd i think what i actually need is the solution to integrate application based server,such as plotly dash or bokeh server in web ui?

Maybe plotly dash can help, is there is any other solution?

CostlyOstrich36 I'm afraid even i change to ClearML, the problem still exists...

But when i click view_all, i can see all the experiments

Also, from the log, I see your ES version is 5.6:

at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:136) ~[elasticsearch-5.6.16.jar:5.6.16]

and I'm not sure why - in v0.16, the ES version is already 7.6, which makes me think your original version was v0.15, also in the new docker-compose the version is 7.16, so maybe you are not using the updated docker-compose file?

It confused me too, but ES dir in my 0.16 version is /opt/trains/data/elastic_7

Do you mean i send the old one to you?

SuccessfulKoala55 It seems ok

And i try to upgrade elastic by your script, but it cannot success, the log shows :

AppetizingMouse58 Ok , i see, thanks!

SuccessfulKoala55
Do you mean even if the json is so large, if i use Logger.report_scatter2d() , it wont cause TransportError(429, 'circuit_breaking_exception ?

This is the second command

May be its due to my curl?

I have remake curl, this commad "sudo curl -L " https://github.com/docker/compose/releases/download/1.24.1/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compos" will work

here is my old docker-compose

AppetizingMouse58

The error is still there for new experiment

Ok, i have reverte the change ,here is two log:

AppetizingMouse58 Ok, this is the full log, here seems a error:

That's ok, i have just start the server. Could you tell me how to delete this index?

AppetizingMouse58 After i modify the max_buckets to 200000000000, I cannot see any information in web ui. Here is the log:

Hi SuccessfulKoala55 I have run this in step 2