This is an automated email from the ASF dual-hosted git repository. ritesh pushed a commit to branch HDDS-10976 in repository https://gitbox.apache.org/repos/asf/ozone.git
commit 5d43571224c7d2b7ddca12ebb6481e690d49b95c Author: Ritesh H Shukla <[email protected]> AuthorDate: Mon Jun 3 17:06:01 2024 +0200 HDDS-10976. Fix outdated reference to Ozone Datanode running within HDFS --- hadoop-hdds/docs/content/start/OnPrem.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hadoop-hdds/docs/content/start/OnPrem.md b/hadoop-hdds/docs/content/start/OnPrem.md index 9633cbbc66..ade54d1537 100644 --- a/hadoop-hdds/docs/content/start/OnPrem.md +++ b/hadoop-hdds/docs/content/start/OnPrem.md @@ -30,7 +30,7 @@ capable of running independently. The components of ozone are the same in both a 1. Ozone Manager - Is the server that is in charge of the namespace of Ozone. Ozone Manager is responsible for all volume, bucket and key operations. 2. Storage Container Manager - Acts as the block manager. Ozone Manager requests blocks from SCM, to which clients can write data. -3. Datanodes - Ozone data node code runs inside the HDFS datanode or in the independent deployment case runs an ozone datanode daemon. +3. Datanodes - Ozone Datanodes is the server that stores all the containers created by SCM. Datanode is the service the handles all data reads and writes from the Ozone Client. ## Setting up an Ozone only cluster --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
