[
https://issues.apache.org/jira/browse/HDDS-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454808#comment-17454808
]
Aravindan Vijayan commented on HDDS-4177:
-----------------------------------------
Some pointers
* A simple handshaking process can be used by Recon at startup. Check highest
container from SCM, and if it is greater than a threshold (let's say 100 more
than Recon's highest known container), then it will download the SCM DB. Else,
it can let the system learn the new containers in the regular way. It is ok to
live with the
[TOCTTOU|https://en.wikipedia.org/wiki/Time-of-check_to_time-of-use] issue here
since Recon will catch up on new containers later.
* Until the handshaking is done, Recon DN report handling cannot begin.
* We need to investigate out if we can use the GRPC based DB download from SCM
instead of HTTP.
> Bootstrap Recon SCM Container DB
> --------------------------------
>
> Key: HDDS-4177
> URL: https://issues.apache.org/jira/browse/HDDS-4177
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Prashant Pogde
> Assignee: Aswin Shakil Balasubramanian
> Priority: Major
>
> On Recon startup, get the latest SCM DB (if needed) and bootstrap the
> container data.
> Check if we can remove logic added in HDDS-5126 to get batch container exist
> check in SCM from Recon.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
