You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by Jack Levin <ma...@gmail.com> on 2014/04/22 19:34:31 UTC
unable to delete rows in some regions
Hey All, I was wondering if anyone had this issue with 0.90.5 HBASE.
I have a table 'img611', I issue delete of keys like this:
hbase(main):004:0> describe 'img611'
DESCRIPTION
ENABLED
{NAME => 'img611', FAMILIES => [{NAME => 'att', BLOOMFILTER => 'ROW',
VERSIONS => '1', COMPRESSION => 'NONE', TTL => '21474836 true
47', BLOCKSIZE => '350000', IN_MEMORY => 'false', BLOCKCACHE =>
'true'}]}
1 row(s) in 3.3440 seconds
hbase(main):003:0> delete 'img611', '611:u4rpx.jpg', 'att:data'
0 row(s) in 0.0210 seconds
hbase(main):005:0> major_compact 'img611'
After compaction completed on a region, the cells are still there,
even tho I am unable to 'get' them anymore.
hbase(main):005:0> get 'img611', '611:u4rpx.jpg'
COLUMN CELL
0 row(s) in 0.0140 seconds
Here is compaction log:
2014-04-22 10:19:38,266 INFO
org.apache.hadoop.hbase.regionserver.Store: Completed major compaction
of 1 file(s), new
file=hdfs://namenode-rd.imageshack.us:9000/hbase/img611/cf0a557ff4030c238fc5a6ad732be45f/att/8509526122540116685,
size=17.7g; total size for store is 17.7g
2014-04-22 10:19:38,266 INFO
org.apache.hadoop.hbase.regionserver.HRegion: completed compaction on
region img611,u4rpx.jpg,1329700235569.cf0a557ff4030c238fc5a6ad732be45f.
after 35mins, 45sec
More here: https://gist.github.com/anonymous/11187852
The store size was 17.7g, and remained the same after compaction. If I
examine hfile I can still see 611:u4rpx.jpg data in it.
Any ideas whats going on?
-Jack
Re: unable to delete rows in some regions
Posted by Jack Levin <ma...@gmail.com>.
Looks like the data got cleaned after I manually issued 'split' --
This might be a bug. Has anyone seen it before?
Originally, here is the log entry that issued after major compact was
called on the table:
2014-04-22 09:31:59,068 DEBUG
org.apache.hadoop.hbase.regionserver.CompactSplitThread: Compaction
(major) requested for
img611,u4rpx.jpg,1329700235569.cf0a557ff4030c238fc5a6ad732be45f.
because User-triggered major compaction; priority=1, compaction queue
size=2
However, split never occurred, and data did not get cleaned.
-Jack
On Tue, Apr 22, 2014 at 10:34 AM, Jack Levin <ma...@gmail.com> wrote:
> Hey All, I was wondering if anyone had this issue with 0.90.5 HBASE.
> I have a table 'img611', I issue delete of keys like this:
>
> hbase(main):004:0> describe 'img611'
> DESCRIPTION
> ENABLED
> {NAME => 'img611', FAMILIES => [{NAME => 'att', BLOOMFILTER => 'ROW',
> VERSIONS => '1', COMPRESSION => 'NONE', TTL => '21474836 true
> 47', BLOCKSIZE => '350000', IN_MEMORY => 'false', BLOCKCACHE =>
> 'true'}]}
> 1 row(s) in 3.3440 seconds
>
> hbase(main):003:0> delete 'img611', '611:u4rpx.jpg', 'att:data'
> 0 row(s) in 0.0210 seconds
>
>
> hbase(main):005:0> major_compact 'img611'
>
> After compaction completed on a region, the cells are still there,
> even tho I am unable to 'get' them anymore.
>
> hbase(main):005:0> get 'img611', '611:u4rpx.jpg'
> COLUMN CELL
> 0 row(s) in 0.0140 seconds
>
> Here is compaction log:
>
> 2014-04-22 10:19:38,266 INFO
> org.apache.hadoop.hbase.regionserver.Store: Completed major compaction
> of 1 file(s), new
> file=hdfs://namenode-rd.imageshack.us:9000/hbase/img611/cf0a557ff4030c238fc5a6ad732be45f/att/8509526122540116685,
> size=17.7g; total size for store is 17.7g
> 2014-04-22 10:19:38,266 INFO
> org.apache.hadoop.hbase.regionserver.HRegion: completed compaction on
> region img611,u4rpx.jpg,1329700235569.cf0a557ff4030c238fc5a6ad732be45f.
> after 35mins, 45sec
>
> More here: https://gist.github.com/anonymous/11187852
>
> The store size was 17.7g, and remained the same after compaction. If I
> examine hfile I can still see 611:u4rpx.jpg data in it.
>
> Any ideas whats going on?
>
> -Jack