[
https://issues.apache.org/jira/browse/HBASE-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Gray updated HBASE-1852:
---------------------------------
Attachment: HBASE-1852-unittest1.patch
Unit test that reproduces something, not sure what. I'm actually able to
perform Gets on all the tables, but checking if they are enabled doesn't work.
Also, it seems that META always puts everything in the bottom half, so the top
region is actually empty. Unit test creates 5 tables, then splits META, all 5
entries go to second META region.
> HConnectionManager.testTableOnlineState will get into infinite loop if more
> than one .META. region
> --------------------------------------------------------------------------------------------------
>
> Key: HBASE-1852
> URL: https://issues.apache.org/jira/browse/HBASE-1852
> Project: Hadoop HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.20.0
> Environment: OSX/Linux
> Reporter: Cosmin Lehene
> Fix For: 0.20.1
>
> Attachments: 0001-Fixed-.META.-split-bug.patch,
> HBASE-1852-unittest1.patch, HBaseMetaSplitIssues.java
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Create 3 tables (preferably on a clean cluster to avoid other potential
> issues)
> Split .META.
> From the master web inteface try to click on the first table - the page will
> not load and refreshing the main page will show lots of requests.
> HBaseAdmin.testTableOnlineState will get into an infinite loop if .META. has
> more than one region. This method should probably use a regular scanner and
> an iterator.
> I guess this issue would also happen with a single .META. region if rrs =
> getRegionServerWithRetries(s) would get an UnknownScannerException (from a
> scanner lease expiration on the region server), but I haven't double checked
> this.
> I attached a java method that you can use as a reference to reproduce the
> behavior. However, since it calls split() on .META. and that is async, you
> might have to run it twice and check that .META. actually splitted before
> getting into the infinite loop.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
