[
https://issues.apache.org/jira/browse/HBASE-10622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914162#comment-13914162
]
Matteo Bertozzi commented on HBASE-10622:
-----------------------------------------
{code}It will help to use job.getStatus().getFailureInfo() if the copy job
failed?{code}
We already get each mapper stack trace in the "main" log if something fail,
but I guess is not bad if we report it again at the end. let me add that
{code}
Another area is to somehow intelligently to estimate the number of copy mappers
needed based on the size and number of files? Similar to DistCp?
{code}
sure, I was thinking to rewrite the file grouping later to keep in
consideration also the locations..
but I guess adding a default number of mappers here is short enough
> Improve log and Exceptions in Export Snapshot
> ----------------------------------------------
>
> Key: HBASE-10622
> URL: https://issues.apache.org/jira/browse/HBASE-10622
> Project: HBase
> Issue Type: Bug
> Components: snapshots
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Fix For: 0.99.0
>
> Attachments: HBASE-10622-v0.patch
>
>
> from the logs of export snapshot is not really clear what's going on,
> adding some extra information useful to debug, and in some places the real
> exception can be thrown
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)