Skip to content

Instantly share code, notes, and snippets.

@justincaldwell
Created May 17, 2016 18:18
Show Gist options
  • Save justincaldwell/adc64750dde3fc51f9c7685320c2daca to your computer and use it in GitHub Desktop.
Save justincaldwell/adc64750dde3fc51f9c7685320c2daca to your computer and use it in GitHub Desktop.

Elasticsearch Options

  1. Three master+data nodes
  • Three r3.xlarge.elasticsearch nodes (4 cpu, 30G memory, 80G ssd)
  • all serve as master and data nodes
  • can't do multi availibility zones
    • aws es service is limited to 2 azs max so if you want to do multiple azs, node count needs to be even
  • $1058 a month
  1. Four master+data nodes
  • same as above but use 4 nodes to get multiple azs
  • this is vulnerable to split brain
  • $1322 a month
  1. Two data nodes, three master nodes
  • Two r3.xlarge.elasticsearch data nodes (4 cpu, 30G memory, 80G ssd)
  • Three t2.medium.elasticsearch master nodes (2 cpu, 4Gb memory, ebs storage [can be as small as os, no data])
  • multi az and split brain prevention
  • scale horizontally by adding data nodes ($350 per new node)
  • no idea if the master node is enough or too much horsepower but we can adjust as necessary
  • ~ $900 a month
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment