[
https://issues.apache.org/jira/browse/HBASE-27230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated HBASE-27230:
-----------------------------
Description: As HBASE-27223 said, if we get a timeout exception, the only
correct way is to abort the region server, as the design of WAL sync, is to
succeed or die, there is no 'failure'. It is usually not a big deal is because
we set a very large default value here, 5 minutes, usually the WAL system will
abort the region server if it can not finish the sync within 5 minutes (was:
As HBASE-27223 said, if here we get a timeout exception, the only correct way
is to abort the region server, as the design of WAL sync, is to succeed or die,
there is no 'failure'. It is usually not a big deal is because we set a very
large default value here, 5 minutes, usually the WAL system will abort the
region server if it can not finish the sync within 5 minutes)
> RegionServer should abort when WAL.sync throws TimeoutIOException.
> ------------------------------------------------------------------
>
> Key: HBASE-27230
> URL: https://issues.apache.org/jira/browse/HBASE-27230
> Project: HBase
> Issue Type: Bug
> Components: wal
> Affects Versions: 3.0.0-alpha-4
> Reporter: chenglei
> Priority: Major
>
> As HBASE-27223 said, if we get a timeout exception, the only correct way is
> to abort the region server, as the design of WAL sync, is to succeed or die,
> there is no 'failure'. It is usually not a big deal is because we set a very
> large default value here, 5 minutes, usually the WAL system will abort the
> region server if it can not finish the sync within 5 minutes
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
