It looks like HBASE-826 as far as I can tell. If you run a scan over
your '.META.' table, do you see any empty info columns or instances of
info:server or info:serverstartcode that do not have an accompanying
info:regioninfo? (untested -> scan ".META.", {COLUMNS => 'info:'}).
My guess is that you do not. Or does the .META. scan list mention the
region at all the region generating the IOE? If not, I think its an
issue with improper deleting (as per HBASE-826). Old entries are coming
up at scan time. My guess is that the old cells are info:server or
info:serverstartcode cells. You could try adding deletes for the row
that is coming up with the IOE -- add a deleteall on that row. If that
doesn't work try renaming the table. If latter works, you know its some
permutation on hbase-826.
HBASE-826 is supposed to be well fixed. We've not seen it in a while so
its interesting that you are seeing it now.
St.Ack
Michael Dagaev wrote:
I will try it.
Can you please explain what exactly that log message means
and why some row range is not accessible ?
Thank you for your cooperation,
M.
On Mon, Jan 5, 2009 at 8:17 PM, stack <[email protected]> wrote:
One thing to try is renaming your table. There are scripts in TRUNK under
the bin directory to do this: rename_table.rb. See head of script for how
to run it. You should be able to copy it back to your 0.18 install and run
it though you might have to make some minor tweaks.
St.Ack
