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
Any Idea What I'Ve Missed Here? Thanks

Any idea what I've missed here? Thanks

  
  
Posted 2 years ago
Votes Newest

Answers 12


could it be due to the deployment wranings I've got

  
  
Posted 2 years ago

thanks CostlyOstrich36 for pointing me to this path - it seems that I had a permission problem on the elastic folder. it seems to work now

  
  
Posted 2 years ago

BattyDove56 , that was my suspicion as well, that's why I wanted to see the logs πŸ™‚

  
  
Posted 2 years ago

CostlyOstrich36 it seems that the elastic server keeps restarting ... 😞

  
  
Posted 2 years ago

BattyDove56 , the warning doesn't seem related. As I mentioned before, you need to check the elastic logs to see what's the issue. post them here so we can look together πŸ™‚

  
  
Posted 2 years ago

give it few seconds an should work. That’s what I’ve experienced πŸ™‚

  
  
Posted 2 years ago

The following command should give you something:
docker logs --follow clearml-elastic

  
  
Posted 2 years ago

yes it is still restarting...

  
  
Posted 2 years ago

CostlyOstrich36 thanks. Where can I find them? /opt/clearml/data/elastic_7 seems to be empty

  
  
Posted 2 years ago

image

  
  
Posted 2 years ago

image

  
  
Posted 2 years ago

Hi BattyDove56 , it looks like your elasticsearch container is restarting. Is this the issue still? Can you check the container logs to see why it's restarting? I think this is what might be causing the issue with ClearML server not raising properly

  
  
Posted 2 years ago