You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Aravindan Vijayan (Jira)" <ji...@apache.org> on 2020/01/06 23:31:00 UTC
[jira] [Updated] (HDDS-2848) Verify Recon works as expected with OM
HA.
[ https://issues.apache.org/jira/browse/HDDS-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aravindan Vijayan updated HDDS-2848:
------------------------------------
Summary: Verify Recon works as expected with OM HA. (was: Verify OM HA works as expected with Recon.)
> Verify Recon works as expected 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
> Priority: Major
>
> Since Recon already uses the OzoneManagerClientProtocol to query the OzoneManager, on an OM HAcluster, the RPC client automatically routes the request to the leader. 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. In this version of Recon, the plan is to test out OM HA scenarios and add unit/integration tests to verify correct behavior
--
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