[
https://issues.apache.org/jira/browse/HBASE-28941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eungsop Yoo updated HBASE-28941:
--------------------------------
Description:
CallTimeoutException and ConnectException might be caused by a network or
hardware issue of that server. We might not be able to connect to that server
for a while. So we have to clear all meta caches of the server on which
hardware failure related exceptions occurred. If we don't clear the caches, we
might get the same exceptions as many times as the number of location caches of
that server.
https://issues.apache.org/jira/browse/HBASE-7590
https://issues.apache.org/jira/browse/HBASE-22261
We already have ClusterStatusPublisher/Listener feature. But it is not possible
to use this feature in some infrastructure environments like me.
was:
CallTimeoutException and ConnectException might be caused by a network or
hardware issue of that server. We might not be able to connect to that server
for a while. So we have to clear all meta caches of the server on which
hardware failure related exceptions occurred. If we don't clear the caches, we
might get the same exceptions as many times as the number of location caches of
that server.
https://issues.apache.org/jira/browse/HBASE-7590
We already have ClusterStatusPublisher/Listener feature. But it is not possible
to use this feature in some infrastructure environments like me.
> Clear all meta caches of the server on which hardware failure related
> exceptions occurred
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-28941
> URL: https://issues.apache.org/jira/browse/HBASE-28941
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 2.4.18, 2.5.10
> Reporter: Eungsop Yoo
> Assignee: Eungsop Yoo
> Priority: Major
> Labels: pull-request-available
>
> CallTimeoutException and ConnectException might be caused by a network or
> hardware issue of that server. We might not be able to connect to that server
> for a while. So we have to clear all meta caches of the server on which
> hardware failure related exceptions occurred. If we don't clear the caches,
> we might get the same exceptions as many times as the number of location
> caches of that server.
>
> https://issues.apache.org/jira/browse/HBASE-7590
> https://issues.apache.org/jira/browse/HBASE-22261
> We already have ClusterStatusPublisher/Listener feature. But it is not
> possible to use this feature in some infrastructure environments like me.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
