不爲也 比不能也

If you’ve been following the normal development path, you’ve probably been playing with Elasticsearch on your laptop or on a small cluster of machines lying around. But when it comes time to deploy Elasticsearch to production, there are a few recommendations that you should consider. Nothing is a hard-and-fast rule; Elasticsearch is used for a wide range of tasks and on a bewildering array of ma..

You should always run the most recent version of the Java Virtual Machine (JVM), unless otherwise stated on the Elasticsearch website. Elasticsearch, and in particular Lucene, is a demanding piece of software. The unit and integration tests from Lucene often expose bugs in the JVM itself. These bugs range from mild annoyances to serious segfaults, so it is best to use the latest version of the J..

If you are using Java, you may wonder when to use the transport client versus the node client. As discussed at the beginning of the book, the transport client acts as a communication layer between the cluster and your application. It knows the API and can automatically round-robin between nodes, sniff the cluster for you, and more. But it is external to the cluster, similar to the REST clients.J..

If you use configuration management already (Puppet, Chef, Ansible), you can skip this tip.이미 설정 관리 도구(configuration management, puppet, chef, ansible 등)를 사용하는 경우, 이 팁을 생략할 수 있다.If you don’t use configuration management tools yet, you should! Managing a handful of servers by parallel-ssh may work now, but it will become a nightmare as you grow your cluster. It is almost impossible to edit 30 con..

Elasticsearch ships with very good defaults, especially when it comes to performance- related settings and options. When in doubt, just leave the settings alone. We have witnessed countless dozens of clusters ruined by errant settings because the administrator thought he could turn a knob and gain 100-fold improvement.Elasticsearch는, 특히 성능과 관련된 설정과 옵션에서, 아주 훌륭한 기본값을 가지고 있다. 확신할 수 없다면, 설정을 그대로 두자..

There are a few hotspots in Elasticsearch that people just can’t seem to avoid tweaking. We understand: knobs just beg to be turned. But of all the knobs to turn, these you should really leave alone. They are often abused and will contribute to terrible stability or terrible performance. Or both.Elasticsearch에서 바꾸지 않아야 하는 설정 몇 가지가 있다. 우리는 조정되어야 하는 설정은 알고 있다. 하지만, 변경하려는 설정 중, 몇 가지는 정말로 그대로 둬야 한다...

The default installation of Elasticsearch is configured with a 1 GB heap. For just about every deployment, this number is usually too small. If you are using the default heap values, your cluster is probably configured incorrectly.Elasticsearch를 기본으로 설치하면, 1 GB의 heap으로 구성된다. 거의 모든 경우에, 일반적으로 이 숫자는 너무 작다. 기본 heap 값을 사용하는 경우, 아마도 cluster는 올바르게 구성되지 않을 것이다.There are two ways to change the heap size..

Lucene uses a very large number of files. At the same time, Elasticsearch uses a large number of sockets to communicate between nodes and HTTP clients. All of this requires available file descriptors.Lucene은 매우 많은 수의 파일을 사용한다. 동시에, Elasticsearch는 node와 HTTP 클라이언트 사이의 통신을 위해 많은 socket을 사용한다. 이것 모두는 사용 가능한 file descriptor가 필요하다.Sadly, many modern Linux distributions ship with a paltry 1,024 file d..

You are likely reading this section before you go into production. The details covered in this chapter are good to be generally aware of, but it is critical to revisit this entire list right before deploying to production. 여러분은 아마도, 제품화 직전에 이 부분을 읽고 있을 것이다. 이 장에서 다루고 있는 세부 사항은 일반적으로 알고 있어도 좋은 내용이다. 그러나, 제품을 배포하기 전에 전체 내용을 다시 한번 확인하는 것이 중요하다. Some of the topics will simply stop you cold (such as ..

Once you have deployed your cluster in production, there are some tools and best practices to keep your cluster running in top shape. In this short chapter, we talk about configuring settings dynamically, tweaking logging levels, improving indexing performance, and backing up your cluster. 제품에 cluster를 배포했다면, cluster를 최상의 상태로 유지하기 위한, 몇 가지 도구와 모범 사례가 있다. 이 장에서는 동적으로 설정을 구성하는 방법, 로깅 수준을 조정하는 방법, ..