The region servers store their write-ahead logs in /hbase/.logs and they are archived .oldlogs, you are probably measuring that too.
J-D On Fri, Dec 9, 2011 at 1:56 PM, Lord Khan Han <[email protected]> wrote: > yes exactly. hadoop dfs -du /hbase its gives us all the table sizes... > funny thing table with lzo size bigger than the exported FILE size also.. > really strange... > > > > > > On Fri, Dec 9, 2011 at 11:53 PM, Jean-Daniel Cryans > <[email protected]>wrote: > >> How are you measuring the size? hadoop dfs -dus /hbase or only that >> table's folder? >> >> J-D >> >> On Fri, Dec 9, 2011 at 1:50 PM, Lord Khan Han <[email protected]> >> wrote: >> > Hi , >> > >> > We are usng CDH3B4 and want to upgrade to CDH3u2. Before doing this >> > we make a separate cluster with same config and installed CDH3u2. >> > >> > We exported our hbase table from cdh3b4 cluster and import it to the >> > new cdh3u2 cluster. Table is LZO and both cluster config is same. >> > >> > After import finished hbase table size doubled!! even its configured >> > to use LZO. We changed table to snappy import again and same result. >> > Table size multiplied x 2 in new cdh3u2 cluster. >> > >> > We didnt find why ? Is there any ideas for this ? >> > >> > thanks >> > >> > Khan >>
