# ElasticSearch index creation is 4 days behind in 6.5.4 **URL:** \ **Category:** Elasticsearch\ **Created:** [January 23, 2019, 6:27pm UTC](https://discuss.elastic.co/t/elasticsearch-index-creation-is-4-days-behind-in-6-5-4/165469 "2019-01-23T18:27:24Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![inf2ravikumar](https://avatars.discourse-cdn.com/v4/letter/i/958977/32.png) [@inf2ravikumar](https://discuss.elastic.co/u/inf2ravikumar)\ **Post date:** [January 23, 2019, 6:27pm UTC](https://discuss.elastic.co/t/elasticsearch-index-creation-is-4-days-behind-in-6-5-4/165469/1 "2019-01-23T18:27:24Z")
I have recently upgraded my production cluster to 6.5.4 Seeing there are so many delays in ingesting high volume logs in Cluster. I'm getting around 3tb from 560 filebeat clients which use multiple prosecutors among them 2 logs are very high volume of logs which generates 1 to 2tb index which shows me they are behind in ingesting here is my current data flow to elasticsearch 560 filebeat =\> 3 Logstash server =\> Elasticsearch Dedicated ingest nodes 4 =\> Data 6 data nodes.. not sure why filebeat or logstash is delaying process any inputs will be helpfull ![51%20PM](https://us1.discourse-cdn.com/elastic/original/3X/c/6/c6887bb3572208a322f9ae73d90186926e74e37e.png) ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [January 23, 2019, 6:38pm UTC](https://discuss.elastic.co/t/elasticsearch-index-creation-is-4-days-behind-in-6-5-4/165469/2 "2019-01-23T18:38:42Z")
What does CPU usage on Logstash and dedicated ingest node look like? What is the specification of your data nodes? What does CPU, disk I/O and iowait look like on these nodes? ---
**Author:** ![inf2ravikumar](https://avatars.discourse-cdn.com/v4/letter/i/958977/32.png) [@inf2ravikumar](https://discuss.elastic.co/u/inf2ravikumar)\ **Post date:** [January 23, 2019, 6:41pm UTC](https://discuss.elastic.co/t/elasticsearch-index-creation-is-4-days-behind-in-6-5-4/165469/3 "2019-01-23T18:41:46Z")
Currently using Dell 720 PoweEdge Servers which as 190G of memory pretty high configuration CPU [root@elk-es-ho-16 ~]# lscpu Architecture: x86\_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 32 On-line CPU(s) list: 0-31 Thread(s) per core: 2 Core(s) per socket: 8 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel CPU family: 6 Model: 45 Model name: Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz Stepping: 7 CPU MHz: 3162.243 CPU max MHz: 3300.0000 CPU min MHz: 1200.0000 BogoMIPS: 5200.04 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 20480K NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant\_tsc arch\_perfmon pebs bts rep\_good nopl xtopology nonstop\_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds\_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4\_1 sse4\_2 x2apic popcnt tsc\_deadline\_timer aes xsave avx lahf\_lm ssbd ibrs ibpb stibp tpr\_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts spec\_ctrl intel\_stibp flush\_l1d [root@elk-es-ho-16 ~]# Thanks / Ravi ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [January 23, 2019, 7:07pm UTC](https://discuss.elastic.co/t/elasticsearch-index-creation-is-4-days-behind-in-6-5-4/165469/4 "2019-01-23T19:07:28Z")
That does not really answer the question. ---
**Author:** ![inf2ravikumar](https://avatars.discourse-cdn.com/v4/letter/i/958977/32.png) [@inf2ravikumar](https://discuss.elastic.co/u/inf2ravikumar)\ **Post date:** [January 23, 2019, 7:28pm UTC](https://discuss.elastic.co/t/elasticsearch-index-creation-is-4-days-behind-in-6-5-4/165469/5 "2019-01-23T19:28:25Z")
Sorry about it didn't read the question properly average is %1000 spikes about 2542 in logstash elasticsearch data nodes about %1327 PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 47120 logstash 39 19 0.148t 0.104t 18020 S 983.4 56.6 3449:40 java PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 17390 elastic+ 20 0 2.885t 0.103t 9.877g S 1327 55.6 101751:57 java Disk space 75TB ![54%20PM](https://us1.discourse-cdn.com/elastic/original/3X/b/6/b6262e5d16166ddf509b81c9ff2e296bbde7158d.png) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 20, 2019, 7:28pm UTC](https://discuss.elastic.co/t/elasticsearch-index-creation-is-4-days-behind-in-6-5-4/165469/6 "2019-02-20T19:28:27Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.