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
Answered
We Are Having The Same Issue As

We are having the same issue as https://github.com/allegroai/clearml/issues/324 with no resolution... any ideas on how to solve this?

  
  
Posted 2 years ago
Votes Newest

Answers 13


Are you getting similar responses from your elasticsearch?

  
  
Posted 2 years ago

Is tehre anything specific about the logs we're looking for? Because if I just dumop them it will take me a while to see no sensitive data and naming is there

  
  
Posted 2 years ago

I had the all shards failed issue before. I had to delete all the errored out workers and queues before eveything went to normal

  
  
Posted 2 years ago

Well, you should see search_phase_execution_exception somewhere, I assume

  
  
Posted 2 years ago

The console log error is related to the elastic search container

  
  
Posted 2 years ago

Can you get the elasticsearch docker-compose service log?

  
  
Posted 2 years ago

Also, are you using the cleanup service?

  
  
Posted 2 years ago

Couldn't agree more SuccessfulKoala55

  
  
Posted 2 years ago

For me a simple restart worked

  
  
Posted 2 years ago

e.g. docker-compose restart

  
  
Posted 2 years ago

I restarted the server and it works now

  
  
Posted 2 years ago

lucky you 🙂

  
  
Posted 2 years ago

I had the all shards failed issue before. I had to delete all the errored out workers and queues before everything went to normal

ImmenseMole41 it's always a good strategy to backup regularly 😕

  
  
Posted 2 years ago