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

Sarveksha Yeshavantha Raju resolved HDDS-10261.
-----------------------------------------------
    Resolution: Resolved

> Fix typos in Architecture documentation
> ---------------------------------------
>
>                 Key: HDDS-10261
>                 URL: https://issues.apache.org/jira/browse/HDDS-10261
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: documentation
>            Reporter: Sarveksha Yeshavantha Raju
>            Assignee: Sarveksha Yeshavantha Raju
>            Priority: Minor
>              Labels: documentation, pull-request-available
>         Attachments: 2. SCM keeps track of all the block replicas. If there 
> is a loss of data node or a.png, An Ozone block contains the container ID and 
> a local ID. The figure below shows the.png, Max time for Recon to wait before 
> it.png, This means that when you want to write some data, you ask Ozone 
> Manager for a.png
>
>
> 1. 
> !This means that when you want to write some data, you ask Ozone Manager for 
> a.png|width=599,height=94! 
> Change: Ozone Manager returns it _to_ you
> 2.
> !2. SCM keeps track of all the block replicas. If there is a loss of data 
> node or a.png|width=602,height=71! 
> Change: SCM detects it and instructs data nodes _to_ make copies 
> 3.
> !An Ozone block contains the container ID and a local ID. The figure below 
> shows the.png|width=591,height=43!
> Change: The figure below shows the logical layout of _the_ Ozone block.
> 4. 
> !Max time for Recon to wait before it.png|width=634,height=41! 
> Change: Max time for Recon to wait before it _exits_ out of safe or warmup 
> mode.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to