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

Ted Yu commented on HBASE-7213:
-------------------------------

Patch v14 looks good.
I ran the following tests locally and they passed:
{code}
  684  mt -Dtest=TestCatalogTrackerOnCluster#testBadOriginalRootLocation 
  685  mt -Dtest=TestUpgradeFromHFileV1ToEncoding#testUpgrade 
  686  mt -Dtest=TestRestartCluster
{code}
There was one test failure which may not be related to the patch:
{code}
testReplayEditsAfterRegionMovedWithMultiCF(org.apache.hadoop.hbase.regionserver.wal.TestWALReplay)
  Time elapsed: 41.99 sec  <<< ERROR!
org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after 
attempts=10, exceptions:
Sat Jan 12 11:25:58 PST 2013, org.apache.hadoop.hbase.client.HTable$3@3c993730, 
org.apache.hadoop.hbase.RegionMovedException: Region moved to: 
hostname=10.120.104.184 port=56941.
Sat Jan 12 11:25:59 PST 2013, org.apache.hadoop.hbase.client.HTable$3@3c993730, 
java.io.IOException: Call to /10.120.104.184:56941 failed on local exception: 
java.io.EOFException
Sat Jan 12 11:26:00 PST 2013, org.apache.hadoop.hbase.client.HTable$3@3c993730, 
java.net.ConnectException: Connection refused
Sat Jan 12 11:26:01 PST 2013, org.apache.hadoop.hbase.client.HTable$3@3c993730, 
org.apache.hadoop.hbase.ipc.HBaseClient$FailedServerException: This server is 
in the failed servers list: /10.120.104.184:56941
Sat Jan 12 11:26:03 PST 2013, org.apache.hadoop.hbase.client.HTable$3@3c993730, 
java.net.ConnectException: Connection refused
Sat Jan 12 11:26:05 PST 2013, org.apache.hadoop.hbase.client.HTable$3@3c993730, 
java.net.ConnectException: Connection refused
Sat Jan 12 11:26:09 PST 2013, org.apache.hadoop.hbase.client.HTable$3@3c993730, 
java.net.ConnectException: Connection refused
Sat Jan 12 11:26:13 PST 2013, org.apache.hadoop.hbase.client.HTable$3@3c993730, 
java.net.ConnectException: Connection refused
Sat Jan 12 11:26:22 PST 2013, org.apache.hadoop.hbase.client.HTable$3@3c993730, 
java.net.ConnectException: Connection refused
Sat Jan 12 11:26:38 PST 2013, org.apache.hadoop.hbase.client.HTable$3@3c993730, 
java.net.ConnectException: Connection refused

  at 
org.apache.hadoop.hbase.client.ServerCallable.withRetries(ServerCallable.java:186)
  at org.apache.hadoop.hbase.client.HTable.get(HTable.java:561)
  at 
org.apache.hadoop.hbase.regionserver.wal.TestWALReplay.testReplayEditsAfterRegionMovedWithMultiCF(TestWALReplay.java:198)
{code}
                
> Have HLog files for .META. 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-2.10.patch, 7213-2.11.patch, 7213-2.12.patch, 
> 7213-2.14.patch, 7213-2.4.patch, 7213-2.6.patch, 7213-2.8.patch, 
> 7213-2.9.patch, 7213-in-progress.2.2.patch, 7213-in-progress.2.patch, 
> 7213-in-progress.patch, 7213v13.txt, 
> TEST-org.apache.hadoop.hbase.catalog.TestCatalogTrackerOnCluster.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

Reply via email to