16GB RAM, 112 memory server with elastic 7.0.15 installed. when ever elastic running the website is going ideal
Welcome!
What is the question or the problem? I don't get it.
We are running the elastic index for 148mm properties, the server config is 16GB RAM, 112 memory , BOT created for the records push. but everytime elastic is going down and the site is not reachable. how to resolve this ? heap allocation is 54 GB
How could you allocate more HEAP than the available RAM?
What is the output of:
GET /
GET /_cat/nodes?v
GET /_cat/health?v
GET /_cat/indices?v
If some outputs are too big, please share them on gist.github.com and link them here.
GET /_cat/nodes?v
ip heap.percent ram.percent cpu load_1m load_5m load_15m node.role master name
192.168.30.7 94 82 44 cdfhilmrstw * ere_elasticsearch_masternode2024
GET /_cat/health?v
epoch timestamp cluster status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent
1710240272 10:44:32 ere_elasticsearchResidential yellow 1 1 91 91 0 0 45 0 66.90%
GET /_cat/indices?v
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
yellow open property_search_emptyresponse fjEXmOU7QoiONnp69mm9tA 5 1 172200 0 60.1mb 60.1mb
yellow open properties_forleases_data_rentroll onqJSNrRTzOMDrcsz2tY3w 5 1 195446 20635 21.8mb 21.8mb
yellow open property_search_inputhistory d4YP18mzQq2wcl4QVatvlw 1 1 9131047 0 3.8gb 3.8gb
green open property_suggest Sg7DjW6ARgSrgesfeElbUA 5 0 1.38E+08 52081203 104gb 104gb
yellow open property_suggest_feb_2024 SYedDdiJSNiY8dOuGkvRmA 1 1 41000 0 16.3mb 16.3mb
yellow open comparablesales_suggest_history UyoLV8h1QkG3hOsGOOgIjA 3 1 1511 9 738kb 738kb
green open .kibana_task_manager_7.15.2_001 UK4g9ftYShOATGFa-LGmYw 1 0 15 11229 1.5mb 1.5mb
green open .apm-custom-link Jv0apkp0SNm2Yjunl6uTPg 1 0 0 0 208b 208b
yellow open owner_contact_company_entity_jan_2024 n2tg7lVMQ6uKrL6nj5PZ1g 1 1 313386 112550 189.3mb 189.3mb
yellow open rentcomparable_feb_2024 AixoeUbiT3aD5mL4mKDk5w 1 1 145470 8723 65.9mb 65.9mb
green open .kibana_7.15.2_001 4S5-OzmcTfK0LIvVeiJPbw 1 0 425 57 2.5mb 2.5mb
yellow open property_search_inputhistory_1 sLOdIoC_QVWNQ2xqTb0AfQ 1 1 348215 0 168.3mb 168.3mb
green open .apm-agent-configuration 1yVliYoBREq9-5i2yUhB2A 1 0 0 0 208b 208b
green open .kibana-event-log-7.15.2-000019 QWoizlp6S2-9g8SsYEscYQ 1 0 5 0 29.5kb 29.5kb
yellow open incentifind_assettype c1ajMF2uTHKAlOjQAkZOXA 1 1 350 0 56.5kb 56.5kb
green open .kibana-event-log-7.15.2-000018 fva5Mh3YQQSH4dCYZVIp4w 1 0 12 0 48.4kb 48.4kb
yellow open crime_search_inputhistory nyr9nuoOQ6aqvu5wEylIwQ 1 1 51 0 49.3kb 49.3kb
green open .kibana-event-log-7.15.2-000017 dF-dvksbSei5oVdyYX27YQ 1 0 4 0 23.7kb 23.7kb
green open .kibana-event-log-7.15.2-000016 68rm-D_kSdCigupT317GFA 1 0 0 0 208b 208b
green open .kibana_task_manager_7.15.0_001 wjrIMbYzRN-LLZezrKC18Q 1 0 15 90305 7.8mb 7.8mb
green open properties_lender_combined_updated_nov_2023 SFi7SXgaR_mdgmxT4preRA 5 0 1.83E+08 40653211 167.1gb 167.1gb
green open .tasks 5ngpfiITTzimzBQ-_LeP0Q 1 0 96 0 93.9kb 93.9kb
yellow open zipcode 6kr1WUjXTGqfb9LlYzQaOQ 1 1 828914 0 86.5mb 86.5mb
yellow open requestcounter DYDW9aZFRS6Xu5WjxNytNQ 1 1 67366 1602 16.5mb 16.5mb
yellow open crimecity e8mOx4ENTC2-FldS0UVnBg 1 1 171 0 27.9kb 27.9kb
yellow open crimesearch_suggest_history 3WIgMEXRRVKJbe6I7bBd4g 3 1 187 0 152.8kb 152.8kb
yellow open salesproperty_urlsearch_inputhistory 7vfRGPr-Tl69EtJKAUZ9KA 1 1 2086 349 803.3kb 803.3kb
green open .monitoring-kibana-7-2024.03.12 XR9FPh9nQIGqoktjbLrK1w 1 0 4146 0 2.4mb 2.4mb
yellow open counties kqSMx4GfSn-FBuaOW9Aytw 1 1 3128 825786 33.9mb 33.9mb
yellow open ownersearch_suggest_history Pi8J1w45Tqqaod4QwDFHdw 3 1 1369 0 423.3kb 423.3kb
green open .kibana-event-log-7.15.0-000022 J7U9CREuSuSLxLm5_83HQQ 1 0 0 0 208b 208b
yellow open city 66yYT-KeQqmkEwDhYfCJ4Q 1 1 205 3065603 73.5mb 73.5mb
green open .kibana-event-log-7.15.0-000024 Xn6tjFPsQdq_6NE8x7-TFg 1 0 0 0 208b 208b
green open .kibana-event-log-7.15.0-000023 Rs_iuZFhS_iLz6Mei7SWbQ 1 0 0 0 208b 208b
green open .kibana-event-log-7.15.0-000025 S_43xp0uQLi8Pj5MhCadYw 1 0 0 0 208b 208b
yellow open apirequestcounter xnv7ulnkSXWMl3QzLQElIA 5 1 568 51 304.5kb 304.5kb
yellow open fairness_suggest_history Vca7s_CATOyTSmPyKbmuhQ 3 1 527 0 187.1kb 187.1kb
green open .geoip_databases vwU17dPBRpCOPYqsdn9Zsw 1 0 39 39 37mb 37mb
yellow open categories BxvKIgBPSs2xHxxluiqYow 1 1 14 0 86.9kb 86.9kb
green open properties_nov_2023 NnjV3V_3T7mNHUrWdkX6lA 5 0 1.4E+08 53119411 290.8gb 290.8gb
green open .kibana_7.15.0_001 3k7xjdoeSQeC2rCiJqOWLQ 1 0 213 20 2.3mb 2.3mb
green open .monitoring-es-7-2024.03.12 UI5PxQPYThKdJtOjwc-zZw 1 0 219496 174710 135.4mb 135.4mb
green open property_suggest_mar_2024 sZ1ouZTpRoOqVGnXRQdaOw 5 0 62108500 0 35.3gb 35.3gb
green open .monitoring-es-7-2024.03.11 fF07_aaMS4CncHcryEnWQA 1 0 476590 241531 246.4mb 246.4mb
yellow open property_urlsearch_inputhistory iyQn4gP7Rp-eN4brhLSgWw 1 1 21664782 0 8.6gb 8.6gb
yellow open fairness_search_inputhistory bwsKl72CTA2gsXlb4dhddQ 1 1 93 0 118.1kb 118.1kb
yellow open crimedata Yn6zn8Y4QNyrGjnw2x4hLQ 1 1 2848729 660640 677.4mb 677.4mb
yellow open property_suggest_history uWhHqxl_TaCV_qJJ_jNVXQ 1 1 235230 45035 76.5mb 76.5mb
green open property_amenities_nov_2023 1ch76N-8S5CTZMoAdbDwSg 5 0 1.7E+08 44467364 28.6gb 28.6gb
Sorry about my late reply , kindly check this and let me know
You did not answer this question.
What is the exact HEAP size?
And
What is the output of:
GET /
Please format your code, logs or configuration files using </> icon as explained in this guide and not the citation button. It will make your post more readable.
Or use markdown style like:
```
CODE
```
This is the icon to use if you are not using markdown format:
There's a live preview panel for exactly this reasons.
Lots of people read these forums, and many of them will simply skip over a post that is difficult to read, because it's just too large an investment of their time to try and follow a wall of badly formatted text.
If your goal is to get an answer to your questions, it's in your interest to make it as easy to read and understand as possible.
I updated your post but please do it for the next one.
Heap is 54 gb,
Right now my elastic monitoring is giving the below message .
{"statusCode":429,"error":"Too Many Requests","message":"[[parent] Data too large, data for [<http_request>] would be [53012957208/49.3gb], which is larger than the limit of [52935137689/49.2gb], real usage: [53012957208/49.3gb], new bytes reserved: [0/0b], usages [request=0/0b, fielddata=1755/1.7kb, in_flight_requests=0/0b, model_inference=0/0b, eql_sequence=0/0b, accounting=31462426/30mb]: circuit_breaking_exception: [circuit_breaking_exception] Reason: [parent] Data too large, data for [<http_request>] would be [53012957208/49.3gb], which is larger than the limit of [52935137689/49.2gb], real usage: [53012957208/49.3gb], new bytes reserved: [0/0b], usages [request=0/0b, fielddata=1755/1.7kb, in_flight_requests=0/0b, model_inference=0/0b, eql_sequence=0/0b, accounting=31462426/30mb]]: [parent] Data too large, data for [<http_request>] would be [53012957208/49.3gb], which is larger than the limit of [52935137689/49.2gb], real usage: [53012957208/49.3gb], new bytes reserved: [0/0b], usages [request=0/0b, fielddata=1755/1.7kb, in_flight_requests=0/0b, model_inference=0/0b, eql_sequence=0/0b, accounting=31462426/30mb]"}Preformatted text
I will get you the details once i do the restart of allthe services
I'm lost.
You said, 16gb RAM, 112 memory, HEAP 54Gb...
Anyway, don't allocate more than 30gb of HEAP.
See Important Elasticsearch configuration | Elasticsearch Guide [8.12] | Elastic
Set
XmsandXmxto no more than 50% of your total memory. Elasticsearch requires memory for purposes other than the JVM heap. For example, Elasticsearch uses off-heap buffers for efficient network communication and relies on the operating system’s filesystem cache for efficient access to files. The JVM itself also requires some memory. It’s normal for Elasticsearch to use more memory than the limit configured with theXmxsetting.
Also upgrade your cluster to at least 7.17 or better 8.12.2.
But then you might still suffer from some memory pressure. You might need to scale out with more nodes and more memory. But I'd first upgrade to see if the newest versions are helping.
Thank you so much
Hi ,
There is one small correction in my config. appologies for that.
Core 16 , 112 GB RAM.
Elastic 1 - 56 indices data , 640GB (data allocation). Node -single node. Heap allocation (54GB)
Elastic 2 - 35 indices data, 240 GB ( data allocation)- single node -Heap allocation (10GB)
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.