devmadhuu opened a new pull request, #5793:
URL: https://github.com/apache/ozone/pull/5793
## What changes were proposed in this pull request?
There is a difference between SCM's IncrementalContainerReportHandler and
Recon's IncrementalContainerReportHandler , Recon always connects to SCM and
verify 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, this PR will
improve below multiple things:
- 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.
## What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-9883
## How was this patch tested?
Tested using existing Junit tests after updating existing test -
`TestReconIncrementalContainerReportHandler`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
