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
Hi! I Have Noticed That Clearml-Elastic Container Consumes 32.82Gib Memory. This Seems

Hi!
I have noticed that clearml-elastic container consumes 32.82GiB Memory. This seems very high (we have a total of 91GiB available -> elastic uses 1/3).
Is this normal? If not, what could be the issue?

Best,
Valentin
image

  
  
Posted 9 days ago
Votes Newest

Answers 5


It seems elastic has allocated a heap of 32GiB, but uses only 4GiB. Where/why have 32GiB been allocated?

  
  
Posted 9 days ago

Can you share the elastic part of your docker container? Are you using any overrides?

  
  
Posted 9 days ago

Last time I tried docker compose, elastic take a lot of RAM !!
You need to limit its RAM usage with mem_limit :

[...]
  elasticsearch:
    networks:
      - backend
    container_name: clearml-elastic
    mem_limit: 2g
    environment:
      bootstrap.memory_lock: "true"
      cluster.name: clearml
[...]
  
  
Posted 9 days ago

ManiacalLizard2 what happens when ES hits the limit? Does it go OOM, or does the scalars loading just take a long time in the web-ui? And what about tasks putting scalars in the index?

  
  
Posted 9 days ago

I think ES use a greedy strategy where it allocate first then use it from there ...

  
  
Posted 9 days ago
46 Views
5 Answers
9 days ago
8 days ago
Tags