[jira] [Assigned] (HDDS-2848) Recon should work with OM HA

["Siddharth Wagle (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDDS-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Siddharth Wagle reassigned HDDS-2848:
-------------------------------------

    Assignee: Siddharth Wagle

> Recon should work with OM HA
> ----------------------------
>
>                 Key: HDDS-2848
>                 URL: https://issues.apache.org/jira/browse/HDDS-2848
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>          Components: Ozone Recon
>            Reporter: Aravindan Vijayan
>            Assignee: Siddharth Wagle
>            Priority: Major
>
> Recon talks to OM in 2 ways - Through HTTP to get DB snapshot, and through RPC to get delta updates.
> Since Recon already uses the OzoneManagerClientProtocol to query the OzoneManager RPC, the RPC client automatically routes the request to the leader on an OM HA cluster. Recon only needs the updates from the OM RocksDB store, and does not need the in flight updates in the OM DoubleBuffer. Due to the guarantee from Ratis that the leader’s RocksDB will always be up to date, Recon does not need to worry about going back in time when a current OM leader goes down. We have to pass in the om service ID to the Ozone Manager client in Recon, and the failover works internally. Currently we pass in 'null'.
> To make the HTTP call to work against OM HA, Recon has to find out the current OM leader and download the snapshot from that OM instance. We can use the way this has been implemented in org.apache.hadoop.ozone.admin.om.GetServiceRolesSubcommand. We can get the roles of OM instances and then determine the leader from that. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org