[
https://issues.apache.org/jira/browse/HBASE-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109705#comment-13109705
]
Lars Hofhansl commented on HBASE-4387:
--------------------------------------
Until then... anybody opposed to this change?
J-D diagnosed the problem correct, I think. And my change should fix it. As
this is a race there is no proof of course.
The only question is whether the first attempt should be logged if it failed,
maybe even at info level so that we can see these cases even without debug
logging.
> 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
