ebuildy
(Thomas Decaux)
March 28, 2022, 8:34am
1
Cluster:
Elasticsearch v7.17.1 running with elastic docker image on kubernetes
6 data nodes: 4 CPUs / 14 Go HEAP / 28 Go memory
Indice: 3 primary shards (+ 1 replica) , 60 Go data
Usage:
nightly full index export, with Apache Spark using elastic for hadoop lib
scroll size: 1200
6 tasks in //
Monitoring:
Question:
All data nodes consume +10Go memory during the long search scroll phase, the heap seems fine, how can I debug what is in this memory please?
This is a problem for us because Spark is running on the same k8s cluster and consume also lot of memory.
warkolm
(Mark Walkom)
March 28, 2022, 8:40am
2
It's likely the OS caching the underlying files that are being requested by Elasticsearch.
ebuildy
(Thomas Decaux)
March 28, 2022, 8:49am
3
Thanks you, I will update our Memory Usage graphs !
BTW, is off-heap Elasticsearch usage reported somewhere?
ebuildy
(Thomas Decaux)
March 28, 2022, 1:48pm
4
Well I am not sure, our infra guys told me page cache is not reported as WSS or RSS, I can graph it and I can see this is not related
blue = cache
yellow = RSS
So the truth is out there
system
(system)
Closed
April 25, 2022, 1:48pm
5
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.