hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16824) Writer.flush() can be called on already closed streams in WAL roll
Date Wed, 19 Oct 2016 06:27:58 GMT

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

Hudson commented on HBASE-16824:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1813 (See [https://builds.apache.org/job/HBase-Trunk_matrix/1813/])
HBASE-16824 Writer.flush() can be called on already closed streams in (enis: rev ef8c65e54201b37edfb9a8f4f4d24137544b8ec1)
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java
* (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestLogRollingNoCluster.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)

Mime
View raw message