You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2016/10/09 13:51:20 UTC
[jira] [Resolved] (HBASE-16685) Revisit execution of SnapshotCopy
in MapReduceBackupCopyService
[ https://issues.apache.org/jira/browse/HBASE-16685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu resolved HBASE-16685.
----------------------------
Resolution: Not A Problem
After code refactoring, this is no longer applicable.
> Revisit execution of SnapshotCopy in MapReduceBackupCopyService
> ---------------------------------------------------------------
>
> Key: HBASE-16685
> URL: https://issues.apache.org/jira/browse/HBASE-16685
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Labels: backup
>
> During code review of backup / restore, Matteo raised comment on the following code:
> {code}
> res = snapshotCp.run(options);
> {code}
> I think this will be a first time where HBase server has a direct dependency on a MR job.
> also we need to revisit this code to avoid having one handler blocked for N hours while we are doing a copy.
> This issue is to address the above comment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)