[
https://issues.apache.org/jira/browse/HBASE-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554697#comment-13554697
]
chunhui shen commented on HBASE-7213:
-------------------------------------
Ted found the failed test in
https://builds.apache.org/job/HBase-TRUNK/3751/testReport/org.apache.hadoop.hbase.regionserver/TestHRegionOnCluster/testDataCorrectnessReplayingRecoveredEdits/
I think the root cause is :
{code}
2013-01-15 18:55:11,132 INFO
[RegionServer:1;minerva.apache.org,57481,1358276108448]
regionserver.HRegionServer(1658): STOPPED: Meta HLog roller thread is no longer
alive -- stop
{code}
>From the code:
{code}
this.metaHLogRoller = new MetaLogRoller(this, this);
String n = Thread.currentThread().getName();
Threads.setDaemonThreadRunning(this.metaHLogRoller.getThread(),
n + "MetaLogRoller", uncaughtExceptionHandler);
{code}
{code}
if (metaHLogRoller != null && !metaHLogRoller.isAlive()) {
stop("Meta HLog roller thread is no longer alive -- stop");
return false;
}
{code}
Should we consider it is possible where metaHLogRoller != null but we haven't
start this thread?
Make an addendum patch.
[~devaraj]
Could you confirm it?
> Have HLog files for .META. and -ROOT- edits only
> ------------------------------------------------
>
> Key: HBASE-7213
> URL: https://issues.apache.org/jira/browse/HBASE-7213
> Project: HBase
> Issue Type: Improvement
> Components: master, regionserver
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Priority: Critical
> Fix For: 0.96.0
>
> Attachments: 7213-15.patch, 7213-2.10.patch, 7213-2.11.patch,
> 7213-2.12.patch, 7213-2.14.patch, 7213-2.14.patch, 7213-2.16.patch,
> 7213-2.4.patch, 7213-2.6.patch, 7213-2.8.patch, 7213-2.9.patch,
> 7213-addendum.patch, 7213-in-progress.2.2.patch, 7213-in-progress.2.patch,
> 7213-in-progress.patch, 7213v13.txt,
> TEST-org.apache.hadoop.hbase.client.TestMultiParallel.xml
>
>
> Over on HBASE-6774, there is a discussion on separating out the edits for
> .META. regions from the other regions' edits w.r.t where the edits are
> written. This jira is to track an implementation of that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
