[ https://issues.apache.org/jira/browse/HDDS-9883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ChenXi updated HDDS-9883: ------------------------- Fix Version/s: 1.4.1 > Recon - Improve the performance of processing of IncrementalContainerReport > requests from DN > -------------------------------------------------------------------------------------------- > > Key: HDDS-9883 > URL: https://issues.apache.org/jira/browse/HDDS-9883 > Project: Apache Ozone > Issue Type: Task > Components: Ozone Recon > Reporter: Devesh Kumar Singh > Assignee: Devesh Kumar Singh > Priority: Major > Labels: pull-request-available > Fix For: 1.5.0, 1.4.1 > > > Between SCM *IncrementalContainerReportHandler* and > *ReconIncrementalContainerReportHandler* , Recon always connecting to SCM and > verifying for each container before adding new container to its own > containerStateManager cache. This could be a bottle neck if SCM may respond > slow and frequent ICR requests may pile up in queue. So as of now, we'll > improve multiple things as part of this JIRA: > * Recon to verify containers in batches from SCM on receive of ICR request > from DNs. > * Reduce the scmClient configs for Recon before connecting to SCM: > ** hdds.scmclient.rpc.timeout - 1 min (Default value is 15 mins) > ** hdds.scmclient.failover.max.retry - 3 (Default value is dynamic and > computed, but based on default values, computed value is 15) > Above 2 SCM client configs will be updated to respective new values > as mentioned for recon to connect to SCM. These 2 SCM client configs will be > exposed and mapped with new recon configs to be able to adjust independently > in recon. > *New configs in Recon:* > * > ** ozone.recon.scmclient.rpc.timeout > ** ozone.recon.scmclient.failover.max.retry > * Merge the Incremental container report (ICR) to existing list of ICR > reports. > -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org For additional commands, e-mail: issues-h...@ozone.apache.org