Details
-
Improvement
-
Status: Patch Available
-
Major
-
Resolution: Unresolved
-
2.4.18, 2.5.10
-
None
-
None
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.
Attachments
Issue Links
- is related to
-
HBASE-22261 Make use of ClusterStatusListener for async client
- Closed
-
HBASE-7590 Add a costless notifications mechanism from master to regionservers & clients
- Closed
- links to