Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doc request - how to create data nodes vs master nodes #393

Closed
spuder opened this issue Nov 21, 2015 · 2 comments
Closed

Doc request - how to create data nodes vs master nodes #393

spuder opened this issue Nov 21, 2015 · 2 comments
Milestone

Comments

@spuder
Copy link
Contributor

spuder commented Nov 21, 2015

It would be nice if the documentation outlined how to create the 3 different types of nodes

  • data
  • master
  • client

From my testing it looks like the following

master

node.data => false
node.master => true

data

# data nodes are default
 node.data => true
 node.master => true

client

node.data => false
node.master => false

Where a full config looks like this:

elasticsearch_configure 'foo-elasticsearch' do
  configuration ({
    'cluster.name' => node['foo-elasticsearch']['config']['cluster_name'],
    'node.name' => Chef::Config[:node_name],
    'node.data' => node['foo-elasticsearch']['config']['node_data'],
    'node.master' => node['foo-elasticsearch']['config']['node_master']
    })
  action :manage
end

Then you can easily create 3 different roles to set the values of node['foo-elasticsearch']['config']['node_data']

  • elasticsearch-master
  • elasticsearch-data
  • elasticsearch-client
@martinb3 martinb3 added the doc label Nov 21, 2015
@martinb3 martinb3 added this to the 2.0.0 release milestone Nov 21, 2015
@martinb3
Copy link
Contributor

I'm happy to document this, but it really isn't something implemented or handled in this cookbook, it's just Elasticsearch's implementation and configuration settings. I am not sure it's worth explaining a setting that this cookbook doesn't actually handle or touch. They are just arbitrary values that get passed through and written to the config file like any other. They are really ES settings, not Chef ones, nor do they have any special attention or handling within Chef.

@martinb3 martinb3 added the ready label Nov 21, 2015
@spuder
Copy link
Contributor Author

spuder commented Nov 21, 2015

Good point. I'm ok if you close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants