Sarveksha Yeshavantha Raju created HDDS-10260:
-------------------------------------------------
Summary: 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
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=518,height=39!
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=639,height=77!
Change: This document _explains_
3. !other one collects all the new requests for the next commit.) To make all
data.png|width=553,height=62!
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=442,height=37!
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=359,height=39!
Change: OM such _as_ nodeId
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
