# Elasticsearch 2.4.0 Cluster issues: **URL:** \ **Category:** Elasticsearch\ **Created:** [October 25, 2016, 2:49pm UTC](https://discuss.elastic.co/t/elasticsearch-2-4-0-cluster-issues/63890 "2016-10-25T14:49:47Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![zero](https://avatars.discourse-cdn.com/v4/letter/z/a88e57/32.png) [@zero](https://discuss.elastic.co/u/zero)\ **Post date:** [October 25, 2016, 2:49pm UTC](https://discuss.elastic.co/t/elasticsearch-2-4-0-cluster-issues/63890/1 "2016-10-25T14:49:47Z")
elasticsearch-2.4.0 Cluster Server configuration : 4 servers （8 core 16G Memory，800G disk with Ali cloud server） shards info: • "number\_of\_shards": "4", • "number\_of\_replicas": "1", the doc is: 512,977,028 docs, total data in cluster :1.01TB (why??) elasticsearch-1.7.1 Cluster Server configuration : 4 servers （8 core 16G Memory，500G disk with Ali cloud server） shards info: • "number\_of\_shards": “5”, • "number\_of\_replicas": "1", the doc is: 520,546,089 docs total data in cluster :751.11G (why??) issues: Data is an application that uses 2 sidekiq to write to the 2 cluster elasticsearch-2.4.0 Cluster: Compared with elasticsearch-1.7.1 Cluster, found a lot of low performance。Disk read and write very frequently （2 cluster is Same write） Figure： **refresh\_interval =1s** elasticsearch-2.4.0 Cluster with iotop: Total DISK READ : 23.38 K/s | Total DISK WRITE : 1694.99 K/s 【Average】 Actual DISK READ: 23.38 K/s | Actual DISK WRITE: 4.52 M/s 【Average】 elasticsearch-1.7.1 Cluster with iotop: Total DISK READ : 66.52 K/s | Total DISK WRITE : 340.43 K/s 【Average】 Actual DISK READ: 66.52 K/s | Actual DISK WRITE: 45.00 K/s 【Average】 elasticsearch-2.4.0 the start: /usr/local/jdk1.8.0\_66/bin/java -Xms12g -Xmx12g -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -XX:+DisableExplicitGC -Dfile.encoding=UTF-8 -Djna.nosys=true -Des.path.home=/data/elasticsearch-node1 -cp /data/elasticsearch-node1/lib/elasticsearch-2.4.0.jar:/data/elasticsearch-node1/lib/\* org.elasticsearch.bootstrap.Elasticsearch start -d elasticsearch-1.7.1 the start: /usr/bin/java -Xms12g -Xmx12g -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -XX:+DisableExplicitGC -Dfile.encoding=UTF-8 -Delasticsearch -Des.path.home=/es/elasticsearch-node1 -cp :/es/elasticsearch-node1/lib/elasticsearch-1.7.1.jar:/es/elasticsearch-node1/lib/:/es/elasticsearch-node1/lib/sigar/ org.elasticsearch.bootstrap.Elasticsearch What is the issues? Why is es-2.4.0 written so frequently? （2 cluster is Same write） from china,thank you! ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 26, 2016, 9:51am UTC](https://discuss.elastic.co/t/elasticsearch-2-4-0-cluster-issues/63890/2 "2016-10-26T09:51:46Z")
The translog is written to disk at each operation in 2.X, that may be why. ---
**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:** [October 26, 2016, 10:10am UTC](https://discuss.elastic.co/t/elasticsearch-2-4-0-cluster-issues/63890/3 "2016-10-26T10:10:51Z")
Are you indexing using bulk requests? Elasticsearch 2.x syncs to disk more frequently compared to Elasticsearch 1.x in order to improve resiliency, which results in more IO, especially if you are not using bulk indexing. The difference in index size may be that doc\_values in Elasticsearch 2.x are enabled by default. This results in larger indices on disk, but significantly reduces heap pressure, which is usually a good tradeoff. ---
**Author:** ![zero](https://avatars.discourse-cdn.com/v4/letter/z/a88e57/32.png) [@zero](https://discuss.elastic.co/u/zero)\ **Post date:** [October 31, 2016, 2:31am UTC](https://discuss.elastic.co/t/elasticsearch-2-4-0-cluster-issues/63890/4 "2016-10-31T02:31:18Z")
we don‘t use bulk requests. Until now still have not found the issues. Elasticsearch5.0 can solve this problem? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 31, 2016, 3:13am UTC](https://discuss.elastic.co/t/elasticsearch-2-4-0-cluster-issues/63890/5 "2016-10-31T03:13:39Z")
Use bulk then! It will help you a lot. ---
**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:** [October 31, 2016, 3:32am UTC](https://discuss.elastic.co/t/elasticsearch-2-4-0-cluster-issues/63890/6 "2016-10-31T03:32:37Z")
Bulk requests has always been the best way to get optimal indexing performance in Elasticsearch. The difference in performance between individual indexing requests and bulk requests is even more pronounced in Elasticsearch 2.x and 5.x due to the changes I described, so I would highly recommend considering bulk requests. ---
**Author:** ![zero](https://avatars.discourse-cdn.com/v4/letter/z/a88e57/32.png) [@zero](https://discuss.elastic.co/u/zero)\ **Post date:** [November 1, 2016, 2:36am UTC](https://discuss.elastic.co/t/elasticsearch-2-4-0-cluster-issues/63890/7 "2016-11-01T02:36:09Z")
Thank you very much. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:08pm UTC](https://discuss.elastic.co/t/elasticsearch-2-4-0-cluster-issues/63890/8 "2017-07-05T22:08:03Z")