不爲也 比不能也

If you are a frequent reader of this blog, you probably know that a lot of effort has already been put into making range queries faster. This time we are going to talk about recent improvements to the specific yet common case of range queries when they are used in conjunctions, ie. when they are ANDed with other queries.이 blog를 자주 접한 독자라면, 이미 range query를 더 빠르게 하기 위해 많은 노력을 했다는 것을 알 것이다. 이번에는 ra..

Elastic Cloud is on the tail end of eliminating a mix of memory issues that has caused problems for a lot of low-memory nodes, and in some rare cases even large nodes. Following the memory problems, we experienced connectivity issues on a handful of servers in eu-west-1 that affected any cluster with at least one node on these impacted servers.Elastic Cloud는 많은 memory가 작은 node와 일부 드문 경우에 큰 node에..

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

Beep… beep… beep… It’s PagerDuty telling you that a node has gone down, or a rack has gone down, or your whole cluster has just rebooted. Either way, your cluster is RED: some shards are not assigned, which means that your data is not fully available.bepp... bepp... bepp... 호출기가 울린다. node 혹은 rack에 장애가 발생했다. 또는 전체 cluster가 reboot 되었다. 어느 쪽이든 cluster가 RED(일부 shard가 할당되지 않았다. 즉, data를 완전히 사용할 수 없다...

When using elasticsearch for larger time data analytics use cases, we recommend using time-based indices and a tiered architecture with 3 different types of nodes (Master, Hot-Node and Warm-Node), which we refer to as the "Hot-Warm" architecture. Each node has their own characteristics, which are described below.더 큰 시간 data 분석 사례에 대해 elasticsearch를 사용할 경우, 시간 기반의 index와 3가지 다른 유형의 node(Master, H..

Like this post? Love numbers and Elasticsearch? I’ll be at Elastic{ON} to meet with attendees face to face and answer your questions. Consider attending the event. Hope to see you there.Imagine being able index your calendar to quickly find all events whose time range conflicts with a proposed event. Or creating a global television guide to find all shows, movies, sports, or broadcasts that are ..

Java programmers have two choices when communicating with Elasticsearch: they can use either the REST API over HTTP, or the internal Java API used by Elasticsearch itself for node-to-node communication.Java programmer는 Elasticsearch와 통신 할 경우, 두 가지 중 하나를 선택을 할 수 있다. HTTP를 통한 REST API 또는 Elasticsearch 자체에서 node 간 통신을 위해 사용하는 내부 Java API를 사용할 수 있다.So, what's the difference between these two APIs? W..

This is the second part of a two-part series about ingest nodes, a new feature in Elasticsearch 5.0.이 글은 Elasticsearch 5.0 의 새로운 기능인 ingest node에 대한 2개의 시리즈 중 두번째 파트이다.In the first part we talked about what ingest nodes are, and how to configure and use them. In this second part we will focus on how to use ingest nodes as part of a deployment of the Elastic Stack.첫 번째 파트에서, ingest node가 무엇이고, 그것..

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

If you have no idea what questions you will want to ask your data when you start ingesting it, columnar storage is probably a good option for you: it helps in two areas that are often close to the heart of users who deal with large amounts of data:data를 index하기 시작할 때, 어떤 query를 해야하는지 잘 모를 경우, 아마도 column 저장소가 좋은 선택일 수 있다. 이는 방대한 양의 data를 처리하는 사용자의 의도와 가까운 2가지 영역에 도움이 된다. Storage efficiency: Since..