Subject: HBase Scan consumes high cpu


Deletes are held in memory. They represent data you have to traverse
until that data is flushed out to disk. When you write a new cell with a
qualifier of 10, that sorts, lexicographically, "early" with respect to
the other qualifiers you've written.

By that measure, if you are only scanning for the first column in this
row which you've loaded with deletes, it would make total sense to me
that the first case is slow and the second fast is fast

Can you please share exactly how you execute your "query" for both(all)
scenarios?

On 9/10/19 11:35 AM, Solvannan R M wrote: