[ https://issues.apache.org/jira/browse/HBASE-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-6478: ---------------------------------- Summary: TestClassLoading.testClassLoadingFromLibDirInJar occasionally fails (was: TestClassLoading.testClassLoadingFromLibDirInJar in coprocessor may appear fail due to waitTableAvailable) > TestClassLoading.testClassLoadingFromLibDirInJar occasionally fails > ------------------------------------------------------------------- > > Key: HBASE-6478 > URL: https://issues.apache.org/jira/browse/HBASE-6478 > Project: HBase > Issue Type: Bug > Components: test > Affects Versions: 0.94.0 > Reporter: zhou wenjian > Fix For: 0.96.0, 0.94.2 > > Attachments: HBASE-6478-trunk.patch, HBASE-6478-trunk-v2.patch, > HBASE-6478-trunk-v3.patch > > > When hudson runs for HBASE-6459, it encounters a failed testcase in > org.apache.hadoop.hbase.coprocessor.TestClassLoading.testClassLoadingFromLibDirInJar. > The link is > https://builds.apache.org/job/PreCommit-HBASE-Build/2455/testReport/org.apache.hadoop.hbase.coprocessor/TestClassLoading/testClassLoadingFromLibDirInJar/ > I check the log, and find that the function waitTableAvailable will only > check the meta table, when rs open the region and update the metalocation in > meta, it may not be added to the onlineregions in rs. > for (HRegion region: > hbase.getRegionServer(0).getOnlineRegionsLocalContext()) { > this Loop will ship, and found1 will be false altogether. > that's why the testcase failed. > So maybe we can hbave some strictly check when table is created -- 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