hbase-issues mailing list archives

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

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

Mikhail Antonov updated HBASE-16824:
------------------------------------
    Fix Version/s: 1.1.8
                   1.2.5
                   1.4.0
                   1.3.0
                   2.0.0

> 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
>             Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.5, 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)

Mime
View raw message