[
https://issues.apache.org/jira/browse/HBASE-16985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15628855#comment-15628855
]
Duo Zhang commented on HBASE-16985:
-----------------------------------
{noformat}
Step 9 : RUN add-apt-repository -y ppa:webupd8team/java
---> Using cache
---> 7b48255864af
Step 10 : RUN apt-get -q update
---> Using cache
---> 76ea3cbf1079
Step 11 : RUN echo oracle-java7-installer shared/accepted-oracle-license-v1-1
select true | sudo /usr/bin/debconf-set-selections
---> Using cache
---> 2807acafc61d
Step 12 : RUN apt-get -q install -y oracle-java7-installer
---> Using cache
---> 2521c81a96ea
Step 13 : RUN echo oracle-java8-installer shared/accepted-oracle-license-v1-1
select true | sudo /usr/bin/debconf-set-selections
---> Using cache
---> 1d640959693e
Step 14 : RUN apt-get -q install --no-install-recommends -y
oracle-java8-installer
---> Running in af39726f88ee
{noformat}
Seems we use cache for all commands before installing java8 which means the
"apt-get -q update" in step 10 is ignored so we can not get the new java8
version...
[~busbey] Is there any way to let yetus force recreate the whole docker image?
Thanks.
> TestClusterId failed due to wrong hbase rootdir
> -----------------------------------------------
>
> Key: HBASE-16985
> URL: https://issues.apache.org/jira/browse/HBASE-16985
> Project: HBase
> Issue Type: Bug
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Priority: Minor
> Attachments: HBASE-16985-branch-1-v1.patch,
> HBASE-16985-branch-1-v1.patch, HBASE-16985-branch-1.patch,
> HBASE-16985-branch-1.patch
>
>
> https://builds.apache.org/job/PreCommit-HBASE-Build/4253/testReport/org.apache.hadoop.hbase.regionserver/TestClusterId/testClusterId/
> {code}
> java.io.IOException: Shutting down
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:230)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:409)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:227)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.<init>(MiniHBaseCluster.java:96)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1071)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1037)
> at
> org.apache.hadoop.hbase.regionserver.TestClusterId.testClusterId(TestClusterId.java:85)
> {code}
> The cluster can not start up because there are no active master. The active
> master can not finish initialing because the hbase:namespace region can not
> be assign.
> In TestClusterId unit test, TEST_UTIL.startMiniHBaseCluster set new hbase
> root dir. But the regionserver thread which stared first used a different
> hbase root dir. If assign hbase:namespace region to this regionserver, the
> region can not be assigned because there are no tableinfo on wrong hbase root
> dir.
> When regionserver report to master, it will get back some new config. But the
> FSTableDescriptors has been initialed so it's root dir didn't changed.
> {code}
> if (LOG.isDebugEnabled()) {
> LOG.info("Config from master: " + key + "=" + value);
> }
> {code}
> I thought FSTableDescriptors need update the rootdir when regionserver get
> report from master.
> The master branch has same problem, too. But the balancer always assign
> hbase:namesapce region to master. So this unit test can passed on master
> branch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
