You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sanjeet Nishad (Jira)" <ji...@apache.org> on 2019/09/25 09:27:00 UTC
[jira] [Assigned] (HBASE-22942) move snapshot verification during
restore / clone into the async master side handling
[ https://issues.apache.org/jira/browse/HBASE-22942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanjeet Nishad reassigned HBASE-22942:
--------------------------------------
Assignee: Sanjeet Nishad
> move snapshot verification during restore / clone into the async master side handling
> -------------------------------------------------------------------------------------
>
> Key: HBASE-22942
> URL: https://issues.apache.org/jira/browse/HBASE-22942
> Project: HBase
> Issue Type: Improvement
> Components: snapshots
> Affects Versions: 1.3.0, 1.4.0, 2.1.0, 2.2.0
> Reporter: Sean Busbey
> Assignee: Sanjeet Nishad
> Priority: Minor
>
> Right now we do snapshot verification prior to queueing the restore / clone request from the client. That means the initial call from the client has to block until we're done. On large manifests (~single digit millions) this easily takes longer than the default timeout of 20 minutes.
>
> Instead we should handle verification as one of the steps in the relevant procedure (hbase 2+) or table handler (hbase 1) so that the master can do it in the background and report status.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)