Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Elasticsearch 5.x

You're reading from   Mastering Elasticsearch 5.x Master the intricacies of Elasticsearch 5 and use it to create flexible and scalable search solutions

Arrow left icon
Product type Paperback
Published in Feb 2017
Publisher Packt
ISBN-13 9781786460189
Length 428 pages
Edition 3rd Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Bharvi Dixit Bharvi Dixit
Author Profile Icon Bharvi Dixit
Bharvi Dixit
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Revisiting Elasticsearch and the Changes 2. The Improved Query DSL FREE CHAPTER 3. Beyond Full Text Search 4. Data Modeling and Analytics 5. Improving the User Search Experience 6. The Index Distribution Architecture 7. Low-Level Index Control 8. Elasticsearch Administration 9. Data Transformation and Federated Search 10. Improving Performance 11. Developing Elasticsearch Plugins 12. Introducing Elastic Stack 5.0

Segment merging under control


Lucene segments are written once and read many times, and data structures, apart from the information about the deleted documents that are held in one of the files, can be changed. After some time, when certain conditions are met, the contents of some segments can be copied to a bigger segment, and the original segments are discarded and thus deleted from the disk. Such an operation is called segment merging.

You may ask yourself, why bother about segment merging? There are a few reasons. First of all, the more segments the index is built from, the slower the search will be and the more memory Lucene will need. In addition to this, segments are immutable, so the information is not deleted from them. If you happen to delete many documents from your index, until the merge happens, these documents are only marked as deleted and are not deleted physically. So, when segment merging happens, the documents that are marked as deleted are not written into the new segment...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime