hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-4387) Error while syncing: DFSOutputStream is closed
Date Tue, 20 Sep 2011 00:09:08 GMT

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

Lars Hofhansl updated HBASE-4387:

    Attachment: 4387.txt

Something like this.
Since the writer is rolled with updateLock held the 2nd invocation will get the correct writer.

We still get the benefit of sync'ing without the lock held most of the time.

(This is a variation of double-checked-locking, but with a 32 bit primitive, so it should
work reliably).

> Error while syncing: DFSOutputStream is closed
> ----------------------------------------------
>                 Key: HBASE-4387
>                 URL: https://issues.apache.org/jira/browse/HBASE-4387
>             Project: HBase
>          Issue Type: Bug
>          Components: wal
>    Affects Versions: 0.92.0
>            Reporter: Todd Lipcon
>            Priority: Critical
>             Fix For: 0.92.0
>         Attachments: 4387.txt, errors-with-context.txt
> In a billion-row load on ~25 servers, I see "error while syncing" reasonable often with
the error "DFSOutputStream is closed" around a roll. We have some race where a roll at the
same time as heavy inserts causes a problem.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message