hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "churro morales (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-11352) When HMaster starts up it deletes the tmp snapshot directory, if you are exporting a snapshot at that time the job will fail
Date Mon, 23 Jun 2014 21:04:24 GMT

     [ https://issues.apache.org/jira/browse/HBASE-11352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

churro morales updated HBASE-11352:
-----------------------------------

    Attachment: HBASE-11352-0.94.patch

Created a configuration option for expiration of in progress snapshots, now master checks
this as well as the modified timestamp for the snapshotInProgress and only deletes when the
snapshot is expired.  Thought 30 days would be a conservative starting value.

This really hurt us when we did an ExportSnapshot that took 1+ week to complete.

> When HMaster starts up it deletes the tmp snapshot directory, if you are exporting a
snapshot at that time the job will fail
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-11352
>                 URL: https://issues.apache.org/jira/browse/HBASE-11352
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.94.19
>            Reporter: churro morales
>         Attachments: HBASE-11352-0.94.patch
>
>
> We are exporting a very large table.  The export snapshot job takes 7+ days to complete.
 During that time we had to bounce HMaster.  When HMaster initializes, it initializes the
SnapshotManager which subsequently deletes the .tmp directory.
> If this happens while the ExportSnapshot job is running the reference files get removed
and the job fails.
> Maybe we could put some sort of token such that when this job is running HMaster wont
reset the tmp directory.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message