hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Yu <yuzhih...@gmail.com>
Subject Re: hbase:meta blocks in L1?
Date Thu, 14 Jul 2016 19:35:09 GMT
Interesting.

Do you want to log a JIRA ?

I checked HTableDescriptor.java in branch-1.1 to branch-1 where
setCacheDataInL1(true) is missing.

The fix would be a one line change.

On Thu, Jul 14, 2016 at 11:43 AM, Lars George <lars.george@gmail.com> wrote:

> Ah wait, this was fixed in
> https://issues.apache.org/jira/browse/HBASE-15467, but is not right
> (if I read this proper) in the 1.x line. It could mean that hbase:meta
> is cached in L2 only.
>
> On Thu, Jul 14, 2016 at 7:37 PM, Ted Yu <yuzhihong@gmail.com> wrote:
> > Looking at FSTableDescriptors#createMetaTableDescriptor() , both column
> > families have the following:
> >
> >                 .setCacheDataInL1(true),
> >
> > Is there something else you were looking for ?
> >
> > Cheers
> >
> > On Thu, Jul 14, 2016 at 6:59 AM, Lars George <lars.george@gmail.com>
> wrote:
> >
> >> Hey,
> >>
> >> HBASE-11364 did add `.setCacheDataInL1(true)`, but the later change to
> >> use `HTableDescriptor.metaTableDescriptor()` changes the layout of the
> >> `hbase:meta` to omit the L1 cache setting. Is this on purpose or an
> >> oversight?
> >>
> >> In other words, are the meta blocks currently never cached in L1?
> >>
> >> Lars
> >>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message