You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2016/11/18 12:33:58 UTC

[jira] [Updated] (HBASE-16824) Writer.flush() can be called on already closed streams in WAL roll

     [ https://issues.apache.org/jira/browse/HBASE-16824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Busbey updated HBASE-16824:
--------------------------------
    Component/s: wal

> 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
>          Components: wal
>            Reporter: Atri Sharma
>            Assignee: Enis Soztutar
>             Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.4, 1.1.8
>
>         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)