不爲也 比不能也

With the development of per-segment search, the delay between indexing a document and making it visible to search dropped dramatically. New documents could be made searchable within minutes, but that still isn’t fast enough.segment별 검색의 개발로, document의 색인과 검색 시에 보이도록 하는 것 사이에 지연이 크게 발생한다. 새로운 document는 수분 내에 검색이 가능하지만, 아직 충분히 빠르지는 않다.The bottleneck is the disk. Commiting a new segment to disk req..

Without an fsync to flush data in the filesystem cache to disk, we cannot be sure that the data will still be there after a power failure, or even after exiting the application normally. For Elasticsearch to be reliable, it needs to ensure that changes are persisted to disk.fsync 없이, filesystem cache에서 디스크로, 데이터를 flush하면, 정전 후에 또는 응용프로그램이 정상적으로 종료된 후에, 데이터가 거기 있다고 확신할 수 없다. 신뢰할 수 있는 Elasticsearc..

With the automatic refresh process creating a new segment every second, it doesn’t take long for the number of segments to explode. Having too many segments is a problem. Each segment consumes file handles, memory, and CPU cycles. More important, every search request has to check every segment in turn; the more segments there are, the slower the search will be.매초마다 자동 refresh 프로세스가 새로운 segment를 ..