[
https://issues.apache.org/jira/browse/HBASE-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711434#comment-14711434
]
Yu Li commented on HBASE-6617:
------------------------------
>From the console output, we could see the core tests failure is caused by the
>zombie test, and from the stack trace we could find a deadlock in MVCC, where
>we're waiting on the same object when synchronize on it:
"main" prio=10 tid=0x00007fb77000a800 nid=0x5004 in Object.wait()
[0x00007fb778799000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000007ee9a5260> (a java.util.LinkedList)
at
org.apache.hadoop.hbase.regionserver.MultiVersionConcurrencyControl.waitForPreviousTransactionsComplete(MultiVersionConcurrencyControl.java:224)
- locked <0x00000007ee9a5260> (a java.util.LinkedList)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalPrepareFlushCache(HRegion.java:2254)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2061)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2026)
at
org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2016)
at
org.apache.hadoop.hbase.regionserver.HRegion.doClose(HRegion.java:1423)
at org.apache.hadoop.hbase.regionserver.HRegion.close(HRegion.java:1344)
- locked <0x00000007ee9c85e8> (a java.lang.Object)
at org.apache.hadoop.hbase.regionserver.HRegion.close(HRegion.java:1295)
at
org.apache.hadoop.hbase.HBaseTestingUtility.closeRegionAndWAL(HBaseTestingUtility.java:352)
at
org.apache.hadoop.hbase.regionserver.TestHRegion.testWritesWhileGetting(TestHRegion.java:3999)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
This is not caused by the changes in this JIRA, and I will open a new one to
track it. And since I'm not familiar with the MVCC part, will expect someone
else to take a look
> 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: HBASE-6617.patch, HBASE-6617_v2.patch,
> HBASE-6617_v3.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)
