[
https://issues.apache.org/jira/browse/HBASE-15446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190751#comment-15190751
]
Anoop Sam John commented on HBASE-15446:
----------------------------------------
Sorry still confusing. So u say here that when the 1st attempt failed to
write to WAL (But actually loaded the file) we will fail the op to the user
app.
And then say
bq.so on next retry we will not find this file to load and will get
FileNotFoundException which I think we can catch that exception and ignore it.
Here we mean HBase code? How we can know whether it is the second trial?
Because the 1st op is failed to user. So the 2nd call also came from user.
If we say back to the user, that the bulk load op is failed, we should be sure
that the load is not actually happened in any of the cluster. Else it will be
very much confusing for the user later.
> Do not abort RS when WAL append for bulk load event marker is failed
> --------------------------------------------------------------------
>
> Key: HBASE-15446
> URL: https://issues.apache.org/jira/browse/HBASE-15446
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.3.0
> Reporter: Ashish Singhi
> Assignee: Ashish Singhi
>
> During bulk load process when the RS fails to append the bulk load event
> marker in WAL we abort that RS which is actually not really required. Instead
> just throw back the exception to the client and let the client retry. This
> will be helpful in case of replication of bulk loaded data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
