[
https://issues.apache.org/jira/browse/HBASE-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108245#comment-13108245
]
Lars Hofhansl commented on HBASE-4387:
--------------------------------------
The writer is closed with the UpdateLock held.
So the failure scenario is that we sync the wrong (closed) writer and if the RS
dies, we end up with WAL entries that were not sync'ed.
A simple fix, then, might be to redo the sync with updateLock held if it failed
the first time, and only throw the exception when it failed the 2nd time.
> 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: 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
