# Speeding up recovery
**URL:** https://discuss.elastic.co/t/speeding-up-recovery/68779
**Category:** Elasticsearch
**Created:** [December 12, 2016, 9:51pm UTC](https://discuss.elastic.co/t/speeding-up-recovery/68779 "2016-12-12T21:51:01Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@steriku](https://discuss.elastic.co/u/steriku)
#### Post date: [December 12, 2016, 9:51pm UTC](https://discuss.elastic.co/t/speeding-up-recovery/68779/1 "2016-12-12T21:51:02Z")
Hi,
I haven't seen any recent threads about this and was wondering if there is any way to speed up recovery on a node that has been restarted where a flush was not done before. I have the settings below but it is still taking a log time.
I have 16 nodes running on 4 servers (8 CPU and 16GB RAM each node), 11\*1.8TB SAS drives and 128GB RAM on each server. This is for a Graylog backend that processes about 50,000 messages/second. Recovery is taking hours and causing my Graylog journal to fill and backup my processing. My shards are about 1.4GB each.
Is there a way to prevent the Elastic Search recovery from slowing down the inserts from Graylog? Would adding more Elastic Search nodes speed up recovery?
Thanks in advance
"persistent": {
"cluster": {
"routing": {
"allocation": {
"node\_concurrent\_recoveries": "8"
}
}
},
"indices": {
"recovery": {
"concurrent\_streams": "8",
"translog\_ops": "500000",
"max\_bytes\_per\_sec": "200mb",
"file\_chunk\_size": "1mb"
}
}
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 9, 2017, 9:51pm UTC](https://discuss.elastic.co/t/speeding-up-recovery/68779/2 "2017-01-09T21:51:15Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.