[일래스틱서치] “Hot-Warm” architecture - 퍼옴

펌질

https://www.elastic.co/blog/hot-warm-architecture

Master nodes

We recommend running 3 dedicated master nodes per cluster having dedicated master nodes which run in their own JVM increases stability and resilience as they are not affected by garbage collection that can affect other types of nodes. These nodes do not handle requests and do not hold any data, and therefore only require less resources (such as CPU, RAM and Disk)

Hot data nodes

Hot data nodes are designed to perform all indexing within the cluster and will also hold the most recent daily indices that generally tend to be queried most frequently. As indexing is a very IO intensive operation, these servers need to be powerful and backed by attached SSD storage.

Warm data nodes

Warm data nodes are designed to handle a large amount of read-only indices that are not queried frequently. As these indices are read-only, warm nodes tend to util

PUT /logs_2015-08-31 { "settings": { "index.routing.allocation.require.box_type" : "hot" } }