[
https://issues.apache.org/jira/browse/HBASE-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408816#comment-13408816
]
Harsh J commented on HBASE-6350:
--------------------------------
In the first hunk, I pre-create the exception, log it and only then throw it.
Previously it was getting thrown directly and was not getting logged before
getting thrown, thereby open to the edge case of client timeout causing an eat
up of the message.
> Some logging improvements for RegionServer bulk loading
> -------------------------------------------------------
>
> Key: HBASE-6350
> URL: https://issues.apache.org/jira/browse/HBASE-6350
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Affects Versions: 0.94.0
> Reporter: Harsh J
> Assignee: Harsh J
> Priority: Minor
> Attachments: HBASE-6350.patch
>
>
> The current logging in the bulk loading RPC call to a RegionServer lacks some
> info in certain cases. For instance, I recently noticed that it is possible
> that IOException may be caused during bulk load file transfer (copy) off of
> another FS and that during the same time the client already times the socket
> out and thereby does not receive a thrown Exception back remotely (HBase
> prints a ClosedChannelException for the IPC when it attempts to send the real
> message, and hence the real cause is lost).
> Improvements around this kind of issue, wherein we could first log the
> IOException at the RS before sending, and a few other wording improvements
> are present in my patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
