You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Arwin S Tio (JIRA)" <ji...@apache.org> on 2019/07/23 06:38:00 UTC

[jira] [Commented] (HBASE-17992) The snapShot TimeoutException causes the cleanerChore thread to fail to complete the archive correctly

    [ https://issues.apache.org/jira/browse/HBASE-17992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890705#comment-16890705 ] 

Arwin S Tio commented on HBASE-17992:
-------------------------------------

Hi all,

If you get a TimeoutException when restoring a snapshot, is that safe to ignore? Doesn't that mean that the restored snapshot has data loss/inconsistencies?

> The snapShot TimeoutException causes the cleanerChore thread to fail to complete the archive correctly
> ------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-17992
>                 URL: https://issues.apache.org/jira/browse/HBASE-17992
>             Project: HBase
>          Issue Type: Bug
>          Components: snapshots
>    Affects Versions: 0.98.10, 1.3.0
>            Reporter: Bo Cui
>            Priority: Major
>         Attachments: hbase-17992-0.98.patch, hbase-17992-1.3.patch, hbase-17992-master.patch, hbase-17992.patch
>
>
> The problem is that when the snapshot occurs TimeoutException  or other Exceptions, there is no correct delete /hbase/.hbase-snapshot/tmp, which causes the cleanerChore to fail to complete the archive correctly.
> Modifying the configuration parameter (hbase.snapshot.master.timeout.millis = 600000) only reduces the probability of the problem occurring.
> So the solution to the problem is: multi-Threaded exceptions or TimeoutExceptions, the Main-thread must wait until all the tasks are finished or canceled, the Main-thread can be cleared /hbase/.hbase-snapshot/tmp/snapshotName.Otherwise the task is likely to write /hbase/.hbase-snapshot/tmp/snapshotName/region - mainfest
> The problem exists in disabledTableSnapshot and enabledTableSnapshot, because I'm currently using the disabledTableSnapshot, so I provide the patch of disabledTableSnapshot



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)