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 one year ago
Votes Newest

Answers 13


Are you getting similar responses from your elasticsearch?

  
  
Posted one year 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 one year ago

Well, you should see search_phase_execution_exception somewhere, I assume

  
  
Posted one year ago

The console log error is related to the elastic search container

  
  
Posted one year ago

Can you get the elasticsearch docker-compose service log?

  
  
Posted one year ago

Also, are you using the cleanup service?

  
  
Posted one year 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 one year ago

Couldn't agree more SuccessfulKoala55

  
  
Posted one year ago

For me a simple restart worked

  
  
Posted one year ago

e.g. docker-compose restart

  
  
Posted one year 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 one year ago

lucky you 🙂

  
  
Posted one year ago

I restarted the server and it works now

  
  
Posted one year ago