>>Assuming mob path is tiny compared to content, do we try to pin blob's
>>metadata
in memory, so that their blocks don't get thrashed by actual MOB blob data
blocks?
Yes, we do. The block cache for the metadata (file path) can be set in the
scan, and the block cache for mob files is in another
Hi.
I'm running dozens of hbase-1.1.5 regionserver for several months.
But they start to show high CPU usages(40~90%) regularly.
It looks like we're experiencing the same issues below:
- https://issues.apache.org/jira/browse/HBASE-16146
- https://issues.apache.org/jira/browse/HBASE-17072
(see
For usecases of that kind we probably should't expect very high block cache
hit rate for data blocks,
but assuming that bloom and index blocks are in memory, 100ms (if that's
not for high percentile) is still a bit high.
>>"it reads the MOB file path from one region"
Assuming mob path is tiny
>>Do we have htrace probes on that codepath? Do we do more seeks that we
expect?
Thanks Mikhail. We don't have htrace on that code path now.
In reading, it reads the MOB file path from one region and then read the
MOB data from that MOB file, and by default the cache on the data block in
MOB files
See http://hbase.apache.org/book.html#_canary. It has lots of options and
is used by various monitoring health of nodes in a cluster.
St.Ack
On Wed, Mar 29, 2017 at 9:57 PM, jeff saremi wrote:
> We have our region servers assigned by Yarn and occasionally we get a
>
Unfamiliar with MOB codebase but reading.. " It takes 100 ms
to retrieve a 1MB cell (file), and only after retrieving I am able to start
serving it to the end user".. Is that avg, p90, p99?
Do we have htrace probes on that codepath? Do we do more seeks that we
expect?
-Mikhail
On Tue, Apr 4,
On Thu, Mar 30, 2017 at 9:25 PM, Daniel Jeliński
wrote:
> Thank you Ted for your response.
>
> I have read that part of HBase book. It never explained why objects over
> 10MB are no good, and did not suggest an alternative storage medium for
> these.
>
>
Thats a hole. I
On Thu, Mar 30, 2017 at 1:01 PM, Daniel Jeliński
wrote:
> ...
> Now. HBase Get in Java API is an atomic operation in the sense that it does
> not complete until all data is retrieved from the server. It takes 100 ms
> to retrieve a 1MB cell (file), and only after retrieving