不爲也 比不能也

Closing / deleting indices while running snapshoteditIn previous versions of Elasticsearch, closing or deleting an index during a full snapshot would make the snapshot fail. In 5.0, the close/delete index request will fail instead. The behavior for partial snapshots remains unchanged: Closing or deleting an index during a partial snapshot is still possible. The snapshot result is then marked as ..

File-system repositories must be whitelistededitLocations of the shared file system repositories and the URL repositories with file: URLs now have to be registered before starting Elasticsearch using the path.repo setting. The path.repo setting can contain one or more repository locations:shared file system repository와 file: 로 시작되는 URL repository의 위치의 URL은 Elasticsearch가 시작되기 전에 path.repo 설정에 등록..

A scroll query is used to retrieve large numbers of documents from Elasticsearch efficiently, without paying the penalty of deep pagination.scroll query는 Elasticsearch에서 매우 많은 수의 document를, deep 페이지 계산의 불이익 없이, 효과적으로 가져오기 위해 함께 사용된다.Scrolling allows us to do an initial search and to keep pulling batches of results from Elasticsearch until there are no more results left. It’s a bit like a cursor ..

As time-based data ages, it becomes less relevant. It’s possible that we will want to see what happened last week, last month, or even last year, but for the most part, we’re interested in only the here and now.시간 기반의 데이터는 오래 될수록, 관련성이 적어진다. 지난 주, 지난 달, 심지어 지난해에 무슨 일이 있었는지 알고 싶을 수도 있지만, 대부분의 경우, 지금, 여기에만 관심이 있다.The nice thing about an index per time frame is that it enables us to easily delete o..

As with any software that stores data, it is important to routinely back up your data. Elasticsearch replicas provide high availability during runtime; they allow you to tolerate sporadic node loss without an interruption of service.데이터를 저장하는 모든 S/W와 마찬가지로, 데이터를 정기적으로 백업하는 것은 중요하다. Elasticsearch의 replica는 실행 시간 동안 고 가용성을 제공하고, 서비스의 중단 없이, 돌발적인 node 손실을 극복할 수 있다.Replicas do not provide protection..

Once you’ve backed up some data, restoring it is easy: simply add _restore to the ID of the snapshot you wish to restore into your cluster:어떤 데이터를 백업했다면, restore은 매우 쉽다. 단순히, cluster에 restore하려는 snapshot의 ID에 _restore 를 추가하면 된다.POST _snapshot/my_backup/snapshot_1/_restoreThe default behavior is to restore all indices that exist in that snapshot. If snapshot_1 contains five indices, all five will..