[
https://issues.apache.org/jira/browse/HBASE-16824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15587944#comment-15587944
]
Hudson commented on HBASE-16824:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-1.1-JDK8 #1882 (See
[https://builds.apache.org/job/HBase-1.1-JDK8/1882/])
HBASE-16824 Writer.flush() can be called on already closed streams in (enis:
rev 4e304b3f919a9000e15fd66df190ab97e63bc07d)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestLogRollingNoCluster.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java
> Writer.flush() can be called on already closed streams in WAL roll
> ------------------------------------------------------------------
>
> Key: HBASE-16824
> URL: https://issues.apache.org/jira/browse/HBASE-16824
> Project: HBase
> Issue Type: Bug
> Reporter: Atri Sharma
> Assignee: Enis Soztutar
> Attachments: hbase-16824_v1.patch, hbase-16824_v2.patch,
> hbase-16824_v2.patch
>
>
> In https://issues.apache.org/jira/browse/HBASE-12074, we hit an error if an
> async thread calls flush on a WAL record already closed as the WAL is being
> rotated. This JIRA investigates if setting the new WAL record path as the
> first operation during WAL rotation will fix the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
