hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stack <st...@duboce.net>
Subject Re: two times more regions after update
Date Wed, 21 Oct 2009 17:27:09 GMT
A better guage would b comparing space occupied in filesystem... do
something like ./bin/hadoop fs -dus /HBASEDIR.  Do it once at 44 regions.
Then do it again, after major compacting when you have 84 regions.  To major
compact manually, run 'tools' in the shell to learn more.

St.Ack

On Wed, Oct 21, 2009 at 7:03 AM, <guillaume.viland@orange-ftgroup.com>wrote:

> Hello, i would appreciate explanations concerning the following point.
> I have an indexed table of 25M rows (44 regions after initial data
> insertion). The IndexedTable has been created with all the default
> attributes except that all columns are set with MaxVersions to 1. Only one
> column is indexed.
> After one whole update of the table with exactly the same data (a kind of
> rewrite of the whole table), the table ended up with 84 regions. In my mind,
> I should have stayed (more or less) with the same amount of region ?
> Thanks in advance.
>
> Guillaume Viland (guillaume.viland@orange-ftgroup.com)
> FT/TGPF/OPF/PORTAIL/DOP Sophia Antipolis
>
>
>
> *********************************
> This message and any attachments (the "message") are confidential and
> intended solely for the addressees.
> Any unauthorised use or dissemination is prohibited.
> Messages are susceptible to alteration.
> France Telecom Group shall not be liable for the message if altered,
> changed or falsified.
> If you are not the intended addressee of this message, please cancel it
> immediately and inform the sender.
> ********************************
>
>

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