[
https://issues.apache.org/jira/browse/HBASE-29265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hernan Gelaf-Romer updated HBASE-29265:
---------------------------------------
Description:
Somewhat related to https://issues.apache.org/jira/browse/HBASE-27487
In HBase 2.X, the AsyncRequestFutureImpl will clear the meta cache if it
receives
was:
Similar to https://issues.apache.org/jira/browse/HBASE-27487
RetriesExhaustedWithDetailsException currently obscures that the underlying
exception(s) may be OperationTimeoutExceededException. Because of this, we can
still run into situations where slow request can trigger a flood of meta cache
clearing exceptions, and hotspot the meta table.
We should update our exception handling logic to special case these exceptions,
and explicitly check to see if the underlying root cause for the request
failures was due to an operation timeout.
> Overloaded cluster can cause meta hotspotting
> ---------------------------------------------
>
> Key: HBASE-29265
> URL: https://issues.apache.org/jira/browse/HBASE-29265
> Project: HBase
> Issue Type: Improvement
> Reporter: Hernan Gelaf-Romer
> Assignee: Hernan Gelaf-Romer
> Priority: Major
> Labels: pull-request-available
>
> Somewhat related to https://issues.apache.org/jira/browse/HBASE-27487
>
> In HBase 2.X, the AsyncRequestFutureImpl will clear the meta cache if it
> receives
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
