Skip to content

Commit afacd38

Browse files
authored
Update README.md on Ceph section (bregman-arie#10220)
1. The "What is the workflow of retrieving data from Ceph?" question was repeated twice. 2. Added the question "What is the workflow of writing data to Ceph?" 3. There was no answer on the workflow on writeing/reading data. They have been added
1 parent f893160 commit afacd38

File tree

1 file changed

+22
-1
lines changed

1 file changed

+22
-1
lines changed

README.md

Lines changed: 22 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3953,10 +3953,31 @@ True
39533953

39543954
<details>
39553955
<summary>What is the workflow of retrieving data from Ceph?</summary><br><b>
3956+
The work flow is as follows:
3957+
3958+
1. The client sends a request to the ceph cluster to retrieve data:
3959+
> **Client could be any of the following**
3960+
>> * Ceph Block Device
3961+
>> * Ceph Object Gateway
3962+
>> * Any third party ceph client
3963+
3964+
3965+
2. The client retrieves the latest cluster map from the Ceph Monitor
3966+
3. The client uses the CRUSH algorithm to map the object to a placement group. The placement group is then assigned to a OSD.
3967+
4. Once the placement group and the OSD Daemon are determined, the client can retrieve the data from the appropriate OSD
3968+
3969+
39563970
</b></details>
39573971

39583972
<details>
3959-
<summary>What is the workflow of retrieving data from Ceph?</summary><br><b>
3973+
<summary>What is the workflow of writing data to Ceph?</summary><br><b>
3974+
The work flow is as follows:
3975+
3976+
1. The client sends a request to the ceph cluster to retrieve data
3977+
2. The client retrieves the latest cluster map from the Ceph Monitor
3978+
3. The client uses the CRUSH algorithm to map the object to a placement group. The placement group is then assigned to a Ceph OSD Daemon dynamically.
3979+
4. The client sends the data to the primary OSD of the determined placement group. If the data is stored in an erasure-coded pool, the primary OSD is responsible for encoding the object into data chunks and coding chunks, and distributing them to the other OSDs.
3980+
39603981
</b></details>
39613982

39623983
<details>

0 commit comments

Comments
 (0)