Creeping memory in Elasticsearch 1.6.0


(Stuart Cracraft) #1

For various reasons, I have to run 1.6.0 of ES.

I've noticed in my memory graphs my ELK cluster (5 nodes) is using 1GB more per day on each node.

cluster.name: elasticsearchlogstashkibana
node.name: "elksrv1"
node.master: true
node.data: true
index.number_of_replicas: 2
index.number_of_shards: 5
network.host: 0.0.0.0
cluster.routing.allocation.node_concurrent_recoveries: 2
indices.recovery.max_bytes_per_sec: 20mb
indices.recovery.compress: false
discovery.zen.minimum_master_nodes: 3
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["elksrv1","elksrv2","elksrv3","elksrv4","elksrv5"]
script.engine.groovy.inline.update: on
http.cors.allow-origin: "/.*/"
http.cors.enabled: true
threadpool.search.queue_size: 10000
cluster.routing.allocation.disk.threshold_enabled: false
cluster.routing.allocation.enable: all

I have thought of adding:

bootstrap.mlockall: true
gateway.recover_after_nodes: 5
gateway.recover_after_time: 5m
gateway.expected_nodes: 5

but haven't.

Any thoughts from anyone on Elasticsearch/ELK clusters memory increasing like this?


(Xavier Facq) #2

Does your cluster store lot of new datas every day or not ?


(Stuart Cracraft) #3

Only about 1.2GB to 1.3GB per day.


(system) #4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.