Adds field data values

[spuder]

Adds filed data values based on this page
http://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-fielddata.html#fielddata-monitoring

[spuder]

I'm pretty new to chef, so I'm not positive this is the right way to add values to the elasticsearch.yaml file. Feedback welcome.

[spuder]

Is there any update on this merge request?

[karmi]

@spuder Sorry, tied with many other things. So, first of all, any key:value pair set in Chef should be automatically inserted into the template, as described in: https://github.com/spuder/cookbook-elasticsearch/blob/patch-1/templates/default/elasticsearch.yml.erb#L9-L15 Does it work for you? Also, we're working on a refactoring of the cookbook (see next branch), so more focused there...

[spuder]

Thanks,

I'm finding that this doesn't work in a wrapper cookbook. This is the correct syntax is it not?

attributes/customize.rb

default[:elasticsearch][:custom_config] = {
  'indices.breaker.fielddata.limit' => '75%',
  'indices.fielddata.cache.size' => '65%'
}

http://stackoverflow.com/questions/29991737/how-do-you-set-node-configurations-in-chef

[karmi]

Yeah, that should work!, but haven't tried it in a wrapper cookbook...

[spuder]

This is a good work around, but it looks like there are 2 elasticsearch.yml files. Chef manages the second one. Took me a while to figure this out.

/usr/local/elasticsearch/conf/elasticsearch.yml
/usr/local/etc/elasticsearch/elasticsearch.yml

Now that I have this workaround, the need for this pull request is significantly reduced. I still think it might be a good value to have in the template since it looks like a common config change.

[martinb3]

Hi there -- we've promoted a new, fully re-written branch to master on this cookbook. We've discovered Github actually automatically closes all PRs when the branch they're made onto is moved. Please re-open if your PR still applies to the re-written cookbook. Thank you!