Trimmed the main elasticsearch.yml configuration file

[karmi]

This patch significantly trims the main elasticsearch.yml configuration file.

The current elasticsearch.yml file is a relic of the past, when Elasticsearch
documentation has been more dispersed and incomplete.

It has improved significantly, so the main configuration can be slimmed down,
and contain only the most important settings for development and production use.

Related: 8d0f1a7

[dakrone]

I still think I favor moving the "discovery" section to right underneath the cluster setting, as minimum_master_nodes is one of the most important settings that needs to be set.

[seang-es]

I agree with @dakrone that Discovery, Gateway and Cluster should be next to each other, as they all relate to cluster topology and would tend to be modified together.

[karmi]

Arguably, setting the node name is even more important (since it doesn't stick after restart otherwise), and also the data/log path (since it's quite probably in a different place then it should be otherwise).

The new file is 100 lines of code, and the assumption is that all settings will be reviewed for a serious deployment. With that in mind, the "Network" section can be moved before "Various" just fine.

[s1monw]

@karmi we discussed this today and we want to move on with what we have. I think we should push what we have (progress over perfection). Given the changes to the config related to scripting and jsonp I guess you should go over it again, can you talk a look at it again?

[karmi]

(...) we want to move on with what we have.

Where by "what we have" we mean this trimmed configuration, or the current master one?

I'll assign the issue to myself, and will review the content against the new changes you mention next week!

[karmi]

Force-pushed a commit rebased against current master.

I was thinking a bit about JSONP, dynamic scripting, etc., but I don't see them as something to add into the concise configuration this pull request proposes.

[dakrone]

I think we should leave out the config for dynamic scripting since we have sandboxing now, enabling it should be a very advanced setting and not something people reach for at the beginning.

[s1monw]

I am pushing this out to 1.5

[clintongormley]

@karmi any chance you can give this a final check and get it merged? thanks

[karmi]

@clintongormley @s1monw So, what can I do to have this merged? I went over the current elasticsearch.yml and I don't see anything to add to this pruned version.

[lukas-vlcek]

@karmi How about updating links elasticsearch.org -> elastic.co ?

[karmi]

@lukas-vlcek Fair point, will do, thanks!

[karmi]

Rebased against master and update the URLs to point to http://elastic.co.

[s1monw]

this looks good to me - I will pull this in now and turn the discussion into discuss if you wanna add not if you wanna remove. I think our config is a settings cheatsheet which we can have separately.

[karmi]

@s1monw Thanks!!