# Elasticsearch restart performance

**URL:** https://discuss.elastic.co/t/elasticsearch-restart-performance/111217
**Category:** Elasticsearch
**Created:** [December 12, 2017, 3:09am UTC](https://discuss.elastic.co/t/elasticsearch-restart-performance/111217 "2017-12-12T03:09:03Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![junkainiu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/junkainiu/32/23928_2.png) [@junkainiu](https://discuss.elastic.co/u/junkainiu)
#### Post date: [December 12, 2017, 3:09am UTC](https://discuss.elastic.co/t/elasticsearch-restart-performance/111217/1 "2017-12-12T03:09:03Z")

</div>

Hi All,  
We are using a one node cluster elasticsearch(version 5.3.0) in a 96RAM 24cores centos7 machine. The cluster holds about 1TB time-based documents in about 30 Indexes. If I restart the cluster using systemctl restart elasticsearch, it takes about 5 minutes to recovery all indexes from red to green. Because the cluster will hold more documents like 10TB in the future , I wonder if there are any methods or settings to speed up the restart process? Following is our index settings, all index settings are the same.

```auto
{
      "index" : {
        "search" : {
          "slowlog" : {
            "threshold" : {
              "fetch" : {
                "warn" : "1s",
                "trace" : "200ms",
                "debug" : "500ms",
                "info" : "800ms"
              },
              "query" : {
                "warn" : "20s",
                "trace" : "2s",
                "debug" : "5s",
                "info" : "10s"
              }
            }
          }
        },
        "indexing" : {
          "slowlog" : {
            "threshold" : {
              "index" : {
                "warn" : "10s",
                "trace" : "500ms",
                "debug" : "2s",
                "info" : "5s"
              }
            }
          }
        },
        "number_of_shards" : "1",
        "provided_name" : "7b2c96f57ea1_nic1_4h_2017121016",
        "creation_date" : "1512892957368",
        "number_of_replicas" : "0",
        "uuid" : "9xm9ZANUS_ufWqGx05EmdQ",
        "version" : {
          "created" : "5030099"
        }
      }
    }
  }

```

---

<div class="post-metadata">

### 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: [December 12, 2017, 3:09am UTC](https://discuss.elastic.co/t/elasticsearch-restart-performance/111217/2 "2017-12-12T03:09:47Z")

</div>

> [@junkainiu](#):
>
> Because the cluster will hold more documents like 10TB in the future , I wonder if there are any methods or settings I can user to speed up the restart process?

Having multiple nodes would speed this up.

---

<div class="post-metadata">

### Author: ![junkainiu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/junkainiu/32/23928_2.png) [@junkainiu](https://discuss.elastic.co/u/junkainiu)
#### Post date: [December 12, 2017, 3:11am UTC](https://discuss.elastic.co/t/elasticsearch-restart-performance/111217/3 "2017-12-12T03:11:28Z")

</div>

Thank you for the quick reply. Do you mean add another machine or use 2 nodes in one machine?

---

<div class="post-metadata">

### 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: [December 12, 2017, 3:12am UTC](https://discuss.elastic.co/t/elasticsearch-restart-performance/111217/4 "2017-12-12T03:12:28Z")

</div>

It depends if you are restarting the Elasticsearch service, or the entire host.

Mind you, you will be lucky to get 10TB to an Elasticsearch node, there are limitations in the JVM that will stop you before that density.

---

<div class="post-metadata">

### Author: ![mujtabahussain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mujtabahussain/32/17514_2.png) [@mujtabahussain](https://discuss.elastic.co/u/mujtabahussain)
#### Post date: [December 12, 2017, 3:13am UTC](https://discuss.elastic.co/t/elasticsearch-restart-performance/111217/5 "2017-12-12T03:13:05Z")

</div>

> [@](#):
>
> Do you mean add another machine or use 2 nodes in one machine?

With that powerful machine, why not try and set up more than one node on that machine! Have a look if you can dockerise your setup!

---

<div class="post-metadata">

### Author: ![junkainiu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/junkainiu/32/23928_2.png) [@junkainiu](https://discuss.elastic.co/u/junkainiu)
#### Post date: [December 12, 2017, 3:15am UTC](https://discuss.elastic.co/t/elasticsearch-restart-performance/111217/6 "2017-12-12T03:15:45Z")

</div>

I am restarting the elatsicsearch service by systemctl. So you mean there is a limitation for the size of the node?

---

<div class="post-metadata">

### Author: ![junkainiu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/junkainiu/32/23928_2.png) [@junkainiu](https://discuss.elastic.co/u/junkainiu)
#### Post date: [December 12, 2017, 3:18am UTC](https://discuss.elastic.co/t/elasticsearch-restart-performance/111217/7 "2017-12-12T03:18:18Z")

</div>

Actually I have tried this and ask question here about the multiple-nodes archtechture. And the results seems it does not help the performance in my situation, the only good is the gc count and time.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 9, 2018, 3:19am UTC](https://discuss.elastic.co/t/elasticsearch-restart-performance/111217/8 "2018-01-09T03:19:09Z")

</div>

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