Aravindan Vijayan created HDDS-5861:
---------------------------------------
Summary: Recon container report processing can slow down when
there are a lot of new containers to consume
Key: HDDS-5861
URL: https://issues.apache.org/jira/browse/HDDS-5861
Project: Apache Ozone
Issue Type: Bug
Components: Ozone Recon
Affects Versions: 1.2.0
Reporter: Aravindan Vijayan
Fix For: 1.3.0
Recon checks and adds a container from SCM whenever it sees it for the first
time. When there are a lot of new containers for Recon to consume due to it
being down for a long time, then this report processing can hang on the RPC
call, or even worse cause more bottleneck issues if SCM is down.
{code}
at
org.apache.hadoop.hdds.scm.protocolPB.StorageContainerLocationProtocolClientSideTranslatorPB.submitRpcRequest(StorageContainerLocationProtocolClientSideTranslatorPB.java:154)
at
org.apache.hadoop.hdds.scm.protocolPB.StorageContainerLocationProtocolClientSideTranslatorPB.submitRequest(StorageContainerLocationProtocolClientSideTranslatorPB.java:144)
at
org.apache.hadoop.hdds.scm.protocolPB.StorageContainerLocationProtocolClientSideTranslatorPB.getContainerWithPipeline(StorageContainerLocationProtocolClientSideTranslatorPB.java:230)
at
org.apache.hadoop.ozone.recon.spi.impl.StorageContainerServiceProviderImpl.getContainerWithPipeline(StorageContainerServiceProviderImpl.java:63)
at
org.apache.hadoop.ozone.recon.scm.ReconContainerManager.checkAndAddNewContainer(ReconContainerManager.java:122)
at
org.apache.hadoop.ozone.recon.scm.ReconContainerReportHandler.onMessage(ReconContainerReportHandler.java:62)
at
org.apache.hadoop.ozone.recon.scm.ReconContainerReportHandler.onMessage(ReconContainerReportHandler.java:38)
at
org.apache.hadoop.hdds.server.events.SingleThreadExecutor.lambda$onMessage$1(SingleThreadExecutor.java:81)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
