hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Amandeep Khurana <ama...@gmail.com>
Subject Re: Region Splits
Date Mon, 21 Nov 2011 01:54:38 GMT
Mark,

Yes, your understanding is correct. If your keys are sequential (timestamps
etc), you will always be writing to the end of the table and "older"
regions will not get any writes. This is one of the arguments against using
sequential keys.

-ak

On Sun, Nov 20, 2011 at 11:33 AM, Mark <static.void.dev@gmail.com> wrote:

> Say we have a use case that has sequential row keys and we have rows
> 0-100. Let's assume that 100 rows = the split size. Now when there is a
> split it will split at the halfway mark so there will be two regions as
> follows:
>
> Region1 [START-49]
> Region2 [50-END]
>
> So now at this point all inserts will be writing to Region2 only correct?
> Now at some point Region2 will need to split and it will look like the
> following before the split:
>
> Region1 [START-49]
> Region2 [50-150]
>
> After the split it will look like:
>
> Region1 [START-49]
> Region2 [50-100]
> Region3 [150-END]
>
> And this pattern will continue correct? My question is when there is a use
> case that has sequential keys how would any of the older regions every
> receive anymore writes? It seems like they would always be stuck at
> MaxRegionSize/2. Can someone please confirm or clarify this issue?
>
> Thanks
>
>
>
>
>

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