HDDS-9883. Recon - Improve the performance of processing IncrementalContainerReport from DN#5793
Conversation
…alContainerReport requests from DN.
|
@sumitagrawl Pls review. |
…alContainerReport requests from DN.
sumitagrawl
left a comment
There was a problem hiding this comment.
@devmadhuu Thanks for working over this, have few comments
|
I'm getting this exception which loosk related to this PR
|
This issue is being tracked at HDDS-10413 |
…IncrementalContainerReport from DN (apache#5793) (cherry picked from commit 6021582) Change-Id: Ic9fa1c235a2c347cf9375f6a1da9a47f5dcba213
…ontainerReport from DN (apache#5793) (cherry picked from commit 6021582)
…ontainerReport from DN (apache#5793) (cherry picked from commit 6021582)
…ontainerReport from DN (apache#5793) (cherry picked from commit 6021582)
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:
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