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
Learning Hbase

You're reading from   Learning Hbase Learn the fundamentals of HBase administration and development with the help of real-time scenarios

Arrow left icon
Product type Paperback
Published in Nov 2014
Publisher
ISBN-13 9781783985944
Length 326 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Shashwat Shriparv Shashwat Shriparv
Author Profile Icon Shashwat Shriparv
Shashwat Shriparv
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. Understanding the HBase Ecosystem FREE CHAPTER 2. Let's Begin with HBase 3. Let's Start Building It 4. Optimizing the HBase/Hadoop Cluster 5. The Storage, Structure Layout, and Data Model of HBase 6. HBase Cluster Maintenance and Troubleshooting 7. Scripting in HBase 8. Coding HBase in Java 9. Advance Coding in Java for HBase 10. HBase Use Cases Index

The HBase delete request

When HBase receives a delete request for some data, it does not delete it immediately. The data that needs to be deleted is marked as a tombstone using the tombstone marker. It is a predicate deletion, which is a feature supported by LSM-trees on which HBase is based. This is done because HFile is immutable, and deletion of this is not available inside HFile on HDFS. One of the major compactions takes place when the marked record or data is discarded, and a new HFile is created without the marked data.

The reading and writing cycle

The following figure shows us how the overall reading and writing is done in HBase:

The reading and writing cycle

As we can see in the preceding figure, whenever a write request is sent, it is first written to WAL and then to MemStore, and when MemStore and WAL reach the threshold, it is flushed to the disk file for persistence. Also, when client needs to read some data, it queries the .META. table and then contacts the specific RegionServer; if data is found, it is...

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