[
https://issues.apache.org/jira/browse/HBASE-28129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-28129:
------------------------------
Description:
Found this when debugging HBASE-28114, it is designed to retry forever but when
aborting a region server, we will stop the rpc client, and it will retry a lot
of times and output a lot of logs, which even cause the Jenkins job OOM…
I think we should throw the exception out directly and give up retry when
aborting the region server.
==== Updated ====
It turns out that the problem is the retry when initialize new shipper failed.
We should stop retrying when region server is already stopped.
was:
Found this when debugging HBASE-28114, it is designed to retry forever but when
aborting a region server, we will stop the rpc client, and it will retry a lot
of times and output a lot of logs, which even cause the Jenkins job OOM…
I think we should throw the exception out directly and give up retry when
aborting the region server.
> Do not retry refreshSources when region server is already stopping
> ------------------------------------------------------------------
>
> Key: HBASE-28129
> URL: https://issues.apache.org/jira/browse/HBASE-28129
> Project: HBase
> Issue Type: Bug
> Components: Replication, rpc
> Reporter: Duo Zhang
> Priority: Major
>
> Found this when debugging HBASE-28114, it is designed to retry forever but
> when aborting a region server, we will stop the rpc client, and it will retry
> a lot of times and output a lot of logs, which even cause the Jenkins job OOM…
> I think we should throw the exception out directly and give up retry when
> aborting the region server.
> ==== Updated ====
> It turns out that the problem is the retry when initialize new shipper
> failed. We should stop retrying when region server is already stopped.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
