# Very slow response in cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [September 13, 2017, 5:34am UTC](https://discuss.elastic.co/t/very-slow-response-in-cluster/100291 "2017-09-13T05:34:46Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Amin1](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@Amin1](https://discuss.elastic.co/u/Amin1)\ **Post date:** [September 13, 2017, 5:34am UTC](https://discuss.elastic.co/t/very-slow-response-in-cluster/100291/1 "2017-09-13T05:34:46Z")
Hi team I have 7 node as follow : 172.24.69.14 22 47 0 0.03 0.02 0.05 - - es-client-02 172.24.69.18 84 98 20 0.45 0.60 0.71 d - es-data-03 172.24.69.13 15 41 0 0.00 0.01 0.05 - - es-client-01 172.24.69.17 99 98 28 0.82 0.97 0.87 d - es-data-02 172.24.69.19 13 36 0 0.03 0.04 0.05 m - es-master-01 172.24.69.20 20 36 3 0.00 0.02 0.05 m \* es-master-02 172.24.69.16 95 98 20 0.51 0.63 0.60 d - es-data-01 I think that my configuration for elastic is Ok but I have some problem : 1- kibana error : Discover: Request Timeout after 30000ms 2- using curl command in any node is very slow and result return mybe aftre 40 sec 3- sometimes my nodes ( Occasionally data node ) become disable and i must enable and satart it with this command : " Systemctl start elasticsearch " 4- after deactivate my nodes, my shard become yellow and red . Please help me to solve this Issues. ---
**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:** [September 13, 2017, 6:49am UTC](https://discuss.elastic.co/t/very-slow-response-in-cluster/100291/2 "2017-09-13T06:49:40Z")
Of your nodes only 3 are data nodes, and it seems these are overloaded. What is the specification of these nodes (CPU cores, RAM, heap, type of storage)? How much data do you have on these nodes? How many indices/shards? ---
**Author:** ![Amin1](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@Amin1](https://discuss.elastic.co/u/Amin1)\ **Post date:** [September 13, 2017, 7:31am UTC](https://discuss.elastic.co/t/very-slow-response-in-cluster/100291/3 "2017-09-13T07:31:33Z")
## cpu for all node is : ## [root@es-client-01 ~]# lscpu Architecture: x86\_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 4 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 45 Model name: Intel(R) Xeon(R) CPU E5-2690 v3 @ 2.60GHz Stepping: 2 CPU MHz: 2596.288 BogoMIPS: 5193.98 Hypervisor vendor: VMware Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 30720K NUMA node0 CPU(s): 0-3 ## RAM for All node : 8G Storage for data node is as follow : /dev/mapper/LS-root 47158788 2964292 44194496 7% / devtmpfs 3990700 0 3990700 0% /dev tmpfs 4001412 0 4001412 0% /dev/shm tmpfs 4001412 8676 3992736 1% /run tmpfs 4001412 0 4001412 0% /sys/fs/cgroup /dev/sdb 2064245920 57993040 1901395280 3% /var/lib/elasticsearch /dev/sda1 1038336 182096 856240 18% /boot tmpfs 800284 0 800284 0% /run/user/0 ---
**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:** [September 13, 2017, 8:21am UTC](https://discuss.elastic.co/t/very-slow-response-in-cluster/100291/4 "2017-09-13T08:21:45Z")
> [@Christian\_Dahlqvist](#): > > How many indices/shards? You can get this through the cat shards and cat indices APIs. If you have X-Pack Monitoring installed, you can look there as well. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 11, 2017, 8:21am UTC](https://discuss.elastic.co/t/very-slow-response-in-cluster/100291/5 "2017-10-11T08:21:48Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.