[ 
https://issues.apache.org/jira/browse/HBASE-5801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262052#comment-13262052
 ] 

Jonathan Hsieh commented on HBASE-5801:
---------------------------------------

Jimmy, before committing I ran test a few times and it seemed to be flaky -- in 
6 runs it passed 3x and failed 2x hanging:

{code}
-------------------------------------------------------------------------------
Test set: org.apache.hadoop.hbase.util.TestHBaseFsck
-------------------------------------------------------------------------------
Tests run: 16, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 717.576 sec 
<<< FAILURE!
testMultipleTableDesc(org.apache.hadoop.hbase.util.TestHBaseFsck)  Time 
elapsed: 600.022 sec  <<< ERROR!
java.lang.Exception: test timed out after 600000 milliseconds
        at java.lang.Thread.sleep(Native Method)
        at 
org.apache.hadoop.hbase.util.TestHBaseFsck.deleteTable(TestHBaseFsck.java:269)
        at 
org.apache.hadoop.hbase.util.TestHBaseFsck.testMultipleTableDesc(TestHBaseFsck.java:968)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
        at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
        at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
        at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
        at 
org.junit.internal.runners.statements.FailOnTimeout$1.run(FailOnTimeout.java:28)
{code}

and also failed with an unable to read .regioninfo error. (didn't save this 
log, sorry)

Mind digging in to make it more robust?

                
> [hbck] Hbck should handle case where some regions have different HTD settings 
> in .regioninfo files  (0.90 specific)
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-5801
>                 URL: https://issues.apache.org/jira/browse/HBASE-5801
>             Project: HBase
>          Issue Type: Improvement
>          Components: hbck
>    Affects Versions: 0.90.7
>            Reporter: Jonathan Hsieh
>            Assignee: Jimmy Xiang
>             Fix For: 0.90.7
>
>         Attachments: hbase_5801_v2.patch
>
>
> Recently, we encountered a case where some regions in a table have different 
> HTableDescriptor settings serialized into HDFS their HRegionInfo .regioninfo 
> file.  hbck expects all HTDs within a table to be the same and currently 
> bails out in this situation.
> We need to either point out a proper set of actions for the user to execute 
> or automatically convert the region to a common HTD (likely the most common 
> on, or possibly the "first one".)
> Not sure if this requires reformatting data but may require closing and 
> restarting a region.
> This issue is hbase 0.90.x specific -- 0.92+ keep all table info in a single 
> .tableinfo file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to