[
https://issues.apache.org/jira/browse/HBASE-11352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14041325#comment-14041325
]
Ted Yu commented on HBASE-11352:
--------------------------------
{code}
+ private static final String SNAPSHOT_INPROGRESS_EXPIRATION_MILLIS_KEY =
+ "hbase.snapshot.inProgress.expiration.timeMillis";
{code}
Expiration would be measured in days. Maybe use different unit for the above
config ?
There're long lines in the patch - line length should be 100 or shorter.
> 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)
