[
https://issues.apache.org/jira/browse/HBASE-22361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bahram Chehrazy updated HBASE-22361:
------------------------------------
Description:
When the server is being aborted or stopped, the server waits for all online
regions to flush and close. And if a region is at the end of opening process,
the openEventHandler throws an exception. However, it fails to remove that
region from the on-line regions and fails to notify the master. This would
prevent the server shutdown loop to exit.
Similarly, if regions that are being closed fail for any region, the
closeEventHandler throws but again, it fails to remove that region from the
on-line list.
was:
The abort timer only get set when the server is aborted. But if the server is
being gracefully stopped and something goes wrong causing an abort, the timer
may not get set, and the shutdown process could take a very long time or
completely stuck the server.
> RegionServer could get stuck during shutdown process
> ----------------------------------------------------
>
> Key: HBASE-22361
> URL: https://issues.apache.org/jira/browse/HBASE-22361
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 3.0.0, 2.2.0
> Reporter: Bahram Chehrazy
> Assignee: Bahram Chehrazy
> Priority: Major
>
> When the server is being aborted or stopped, the server waits for all online
> regions to flush and close. And if a region is at the end of opening process,
> the openEventHandler throws an exception. However, it fails to remove that
> region from the on-line regions and fails to notify the master. This would
> prevent the server shutdown loop to exit.
> Similarly, if regions that are being closed fail for any region, the
> closeEventHandler throws but again, it fails to remove that region from the
> on-line list.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
