I've recently encountered a heavy logging use case where a single node among about 10 data nodes had extremely high bulk rejection rates and GC issues.

It turned out that all of the refresh interval settings were completely dependent on the node setting, and the one node experiencing issues was set to "-1".

Adding the intentional refresh interval to the index templates remediated the problem.

Is it still the case that there are scenarios in which disabling refresh is beneficial on the whole? Would it be worth considering removing the ability to do so? If so, then the same thing could be accomplished by setting it to an arbitrarily large time span. Perhaps that should have a max value?

@clintongormley

Elasticsearch version: 2.3.4