[
https://issues.apache.org/jira/browse/HBASE-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113594#comment-13113594
]
stack commented on HBASE-4387:
------------------------------
I think we should try the patch. Seems like the incidence is low. If so,
should we continue to log its happening? Or, I suppose, there is no need since
the second call will throw an IOE if it fails?
Let me commit for now ahead of testing. We can reopen if still a prob. or has
new manifestation.
> 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
> Assignee: Lars Hofhansl
> 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
