不爲也 比不能也

Running Elasticsearch 2.0? Check out this updated post about performance considerations for Elasticsearch 2.0 indexing. Elasticsearch 2.0을 운영 중이라면? Elasticsearch 2.0 indexing에 대한 성능 고려 사항에서 update된 post를 확인해 보자. Elasticsearch users have delightfully diverse use cases, ranging from appending tiny log-line documents to indexing Web-scale collections of large documents, and maximizing indexing thro..

Use bulk requests Bulk requests will yield much better performance than single-document index requests. In order to know the optimal size of a bulk request, you should run a benchmark on a single node with a single shard. First try to index 100 documents at once, then 200, then 400, etc. doubling the number of documents in a bulk request in every benchmark run. When the indexing speed starts to ..

Cluster-health is at one end of the spectrum—a very high-level overview of everything in your cluster. The node-stats API is at the other end. It provides a bewildering array of statistics about each node in your cluster.cluster-health 는 cluster의 모든 것에 대한 매우 높은 수준의 개요 부분이다. node-stats API는 또 다른 부분이다. 이것은 cluster의 각 node에 대한 복잡한 통계의 배열을 제공한다.Node-stats provides so many stats that, until you are a..

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..