Enis Soztutar updated HBASE-16824:
    Attachment: hbase-16824_v2.patch

Fixed the deadlock case. It was due to an earlier version of the v2 patch. 
v2 makes it so that we use a volatile instead of the AtomicLong counter. 

Run the test 20 times. Seems good to go. 

> 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
> 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

Reply via email to