不爲也 比不能也

What If..."What if" questions are fun. "What if you had a time machine: when would you visit?" "What if you had one wish and it would come true: what would it be?" They're the types of hypothetical questions you can ask at a dinner party and get insights about what interests and motives somebody has if barriers were broken down. A few years ago at Elastic, we asked ourselves a "what if" that we ..

Elasticsearch provides failover capabilities by keeping multiple copies of your data in the cluster. In presence of network disruptions or failing nodes, changes might not make it to all the copies. This blog post showcases one of the internal mechanics of Elasticsearch to identify shard copies that are missing changes, providing an in-depth view on how two central components, the consensus modu..

Here are some great slides from our Core Elasticsearch: Operations course that help explain the concept. We'd recommend that you take the full course to understand this even better, but I'll provide an overview from our training here:다음은 Core Elasticsearch: Operations 과정(개념을 설명하는)에서 제공하는 몇 개의 멋진 slide이다. 이 내용을 더 잘 이해하기 위해서는 전체 과정을 수강하는 것이 좋겠지만, 여기에서 과정의 개요를 제공한다.Shard allocation is the process o..

Engineers can resist anything except giving their processes more resources: bigger, better, faster, more of cycles, cores, RAM, disks and interconnects! When these resources are not a bottleneck, this is wasteful but harmless. For processes like Elasticsearch that run on the JVM, the luring temptation is to turn the heap up; what harm could possibly come from having more heap? Alas, the story is..

Throughout this chapter we have spoken about many of the ways that Elasticsearch can scale. Most scaling problems can be solved by adding more nodes. But one resource is finite and should be treated with respect: the cluster state.이 장 전반에 걸쳐, Elasticsearch를 확장하는 많은 방법에 대해 이야기했다. 대부분의 확장 문제는 더 많은 node를 추가하여 해결할 수 있다. 그러나, 어떤 자원은 유한하고 고려되어야 한다. 그것이 cluster state이다.The cluster state is a data struc..