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

Ted Yu commented on HBASE-6617:
-------------------------------

Ran branch-1 test suite locally:
{code}
testWalRecoverLease(org.apache.hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures)
  Time elapsed: 312.545 sec  <<< ERROR!
org.junit.runners.model.TestTimedOutException: test timed out after 60000 
milliseconds
        at sun.misc.Unsafe.park(Native Method)
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
        at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
        at 
org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.pushData(WALProcedureStore.java:484)
        at 
org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.insert(WALProcedureStore.java:335)
        at 
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.submitProcedure(ProcedureExecutor.java:629)
        at 
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.submitProcedure(ProcedureExecutor.java:580)
        at 
org.apache.hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures.testWalRecoverLease(TestMasterFailoverWithProcedures.java:142)
{code}
The above failure is not related to the patch.

> ReplicationSourceManager should be able to track multiple WAL paths
> -------------------------------------------------------------------
>
>                 Key: HBASE-6617
>                 URL: https://issues.apache.org/jira/browse/HBASE-6617
>             Project: HBase
>          Issue Type: Improvement
>          Components: Replication
>            Reporter: Ted Yu
>            Assignee: Yu Li
>             Fix For: 2.0.0, 1.3.0
>
>         Attachments: 6617-v11.patch, HBASE-6617.branch-1.patch, 
> HBASE-6617.branch-1.v2.patch, HBASE-6617.branch-1.v2.patch, 
> HBASE-6617.branch-1.v2.patch, HBASE-6617.patch, HBASE-6617_v10.patch, 
> HBASE-6617_v11.patch, HBASE-6617_v12.patch, HBASE-6617_v2.patch, 
> HBASE-6617_v3.patch, HBASE-6617_v4.patch, HBASE-6617_v7.patch, 
> HBASE-6617_v9.patch
>
>
> Currently ReplicationSourceManager uses logRolled() to receive notification 
> about new HLog and remembers it in latestPath.
> When region server has multiple WAL support, we need to keep track of 
> multiple Path's in ReplicationSourceManager



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to