You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2019/05/01 18:09:00 UTC
[jira] [Updated] (HBASE-22347) try to archive WALs when closing a
region or when shutting down RS
[ https://issues.apache.org/jira/browse/HBASE-22347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Shelukhin updated HBASE-22347:
-------------------------------------
Description:
When RS shuts down in an orderly manner due to an upgrade or decom, even it has 0 regions (discovered when testing HBASE-22254), it still dies with some active WALs.
WALs are then split by master, and in the 0-region case the recovered edits are not used for anything. This splitting is a waste of time... if some region is moved away from the server it might also make sense to archive the WALs to avoid reading the extras.
RS shutdown should archive WALs if possible after flushing/closing regions; given that the latter can fail, perhaps once before, and once after.
Closing a region via an RPC should also try to archive WAL.
was:
When RS shuts down in an orderly manner due to an upgrade or decom, even it has 0 regions (discovered when testing HBASE-22254), it still dies with some active WALs.
WALs are then split by master, and in the 0-region case the recovered edits are not used for anything.
RS shutdown should archive WALs if possible after flushing/closing regions; given that the latter can fail, perhaps once before, and once after.
Closing a region via an RPC should also try to archive WAL.
> try to archive WALs when closing a region or when shutting down RS
> ------------------------------------------------------------------
>
> Key: HBASE-22347
> URL: https://issues.apache.org/jira/browse/HBASE-22347
> Project: HBase
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Priority: Major
>
> When RS shuts down in an orderly manner due to an upgrade or decom, even it has 0 regions (discovered when testing HBASE-22254), it still dies with some active WALs.
> WALs are then split by master, and in the 0-region case the recovered edits are not used for anything. This splitting is a waste of time... if some region is moved away from the server it might also make sense to archive the WALs to avoid reading the extras.
> RS shutdown should archive WALs if possible after flushing/closing regions; given that the latter can fail, perhaps once before, and once after.
> Closing a region via an RPC should also try to archive WAL.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)