You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Attila Doroszlai (Jira)" <ji...@apache.org> on 2024/01/31 20:39:00 UTC
[jira] [Resolved] (HDDS-10260) Update OM High Availability documentation
[ https://issues.apache.org/jira/browse/HDDS-10260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Attila Doroszlai resolved HDDS-10260.
-------------------------------------
Resolution: Fixed
> Update OM High Availability documentation
> -----------------------------------------
>
> Key: HDDS-10260
> URL: https://issues.apache.org/jira/browse/HDDS-10260
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: documentation
> Reporter: Sarveksha Yeshavantha Raju
> Assignee: Sarveksha Yeshavantha Raju
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Attachments: Before bootstrapping a new OM node, all the existing OM's on-disk configuration file.png, Ozone has two metadata-manager nodes (Ozone Manager for key space.png, The details of this approach discussed in a separated design doc but it's integral part.png, This document explain the HA setup of Ozone Manager (OM) HA, please check this.png, other one collects all the new requests for the next commit.) To make all data.png
>
>
> The following screenshots have typos which needs to be fixed.
> 1.
> !Ozone has two metadata-manager nodes (Ozone Manager for key space.png|width=598,height=45!
> Change: Storage Container _Manager_ for block space management
> 2. !This document explain the HA setup of Ozone Manager (OM) HA, please check this.png|width=598,height=72!
> Change: This document _explains_
> 3. !other one collects all the new requests for the next commit.) To make all data.png|width=598,height=67!
> Change: To make all data available for the next request even if the background process _has not yet written_ them the key data is cached in the memory.
> 4. !The details of this approach discussed in a separated design doc but it's integral part.png|width=597,height=50!
> Change: The details of this approach _are_ discussed in a _separate_ design doc but it’s _an_ integral part of the OM HA design.
> 5. !Before bootstrapping a new OM node, all the existing OM's on-disk configuration file.png|width=598,height=65!
> Change: OM such _as_ nodeId
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org