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
Profile picture
ResponsiveKoala38
Moderator
0 Questions, 7 Answers
  Active since 11 July 2024
  Last activity one month ago

Reputation

0
0 Hey, Everyone! Recently I Tried To Restore Clearml From Backup And Encountered Elastic Error. I Decided To Rule Out That Problem Is In Backup And Just Did Fresh Installation Of Clearml Without Backup Files. Problem Persisted. Apiserver Container Logs Read

Hi @<1526734383564722176:profile|BoredBat47> , it seems that your Elasticsearch version is out of sync with what the latest version of the apiserver requires (7.17.18). Can you please follow the instructions here to make sure that you use the latest images for the ClearML Server?
None

10 days ago
0 Hey, Everyone! Recently I Tried To Restore Clearml From Backup And Encountered Elastic Error. I Decided To Rule Out That Problem Is In Backup And Just Did Fresh Installation Of Clearml Without Backup Files. Problem Persisted. Apiserver Container Logs Read

The path then would be as following:

  • Upgrade the old deployment to the latest clearml server according to the clearml server upgrade procedure. This will automatically upgrade the data
  • Backup your data folders (mongo and elastic)
  • Deploy the latest clearml server on another machine and restore the data from the backup
10 days ago
0 Hey, Everyone! Recently I Tried To Restore Clearml From Backup And Encountered Elastic Error. I Decided To Rule Out That Problem Is In Backup And Just Did Fresh Installation Of Clearml Without Backup Files. Problem Persisted. Apiserver Container Logs Read

clearml:1 as well as clearml:latest point to the latest version which is 1.16.2:
None
This version is not able to work with the version of Elasticsearch that you use. I suggest to use the docker compose from the latest version that uses the updated versions of all the required infrastructure

10 days ago
0 Hey, Everyone! Recently I Tried To Restore Clearml From Backup And Encountered Elastic Error. I Decided To Rule Out That Problem Is In Backup And Just Did Fresh Installation Of Clearml Without Backup Files. Problem Persisted. Apiserver Container Logs Read

Can you please describe what working deployments you current have and what is you final goal?
Do you have an old deployment working or it was corrupted?
Do you want to upgrade that old deployment to a new one? Or you want to have a new deployment in some other place based on the data from the old deployment?

10 days ago