Skip to content

Latest commit

 

History

History
11 lines (10 loc) · 963 Bytes

CapacityPlanning.md

File metadata and controls

11 lines (10 loc) · 963 Bytes

Capacity Planning

  • How many nodes?
  • The basic starting point is two nodes with 2 cores and 4GB of memory on each node
  • For fault tolerance perspective three nodes is more appropriate for any cluster
  • What's better more nodes or bigger nodes?
  • More nodes equals IO, Memory, and GC (garbage collector) distributed processing
  • Bigger nodes means more processing can be performed on a node with fast access to in-memory data and faster local IO
  • Resizing node in production is likely more challenging than adding a new node to the cluster
  • ElasticSearch is built for scaling out on commodity hardware, not up on a single massive machine
  • How high can ElasticSearch go? Pretty high