[
https://issues.apache.org/jira/browse/HBASE-11082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984897#comment-13984897
]
Hudson commented on HBASE-11082:
--------------------------------
FAILURE: Integrated in HBase-TRUNK #5124 (See
[https://builds.apache.org/job/HBase-TRUNK/5124/])
HBASE-11082 Potential unclosed TraceScope in FSHLog#replaceWriter() (ndimiduk:
rev 1590997)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java
> Potential unclosed TraceScope in FSHLog#replaceWriter()
> -------------------------------------------------------
>
> Key: HBASE-11082
> URL: https://issues.apache.org/jira/browse/HBASE-11082
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.99.0
> Reporter: Ted Yu
> Assignee: Nick Dimiduk
> Priority: Minor
> Fix For: 0.99.0
>
> Attachments: HBASE-11082.00.patch
>
>
> In the finally block starting at line 924:
> {code}
> } finally {
> // Let the writer thread go regardless, whether error or not.
> if (zigzagLatch != null) {
> zigzagLatch.releaseSafePoint();
> // It will be null if we failed our wait on safe point above.
> if (syncFuture != null) blockOnSync(syncFuture);
> }
> scope.close();
> {code}
> If blockOnSync() throws IOException, the TraceScope would be left unclosed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
