[
https://issues.apache.org/jira/browse/HDDS-15380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-15380:
-------------------------------
Description:
Both S3A and OFS are Hadoop-compatible file system that can be used on Ozone.
Each protocols have their own use cases and we should document it to inform
users which protocols would fit their use cases.
For example, OFS should be faster than S3A since it does not need another proxy
(i.e. S3G) in the data path. However, S3A can support per-bucket configuration
(i.e. for hybrid-cloud scenario or multiple S3 providers). S3A also can be used
on OBJECT_STORE bucket (although there is a price such as directory markers
mechanism, etc) although but OFS has been restricted to only run on LEGACY and
FSO bucket layouts.
We can write a document to compare these documents and add a link to the base
S3A and OFS documentation.
was:
Both S3A and OFS are Hadoop-compatible file system that can be used on Ozone.
Each protocols have their own use cases.
For example, OFS should be faster than S3A since it does not need another proxy
(i.e. S3G) in the data path. However, S3A can support per-bucket configuration
(i.e. for hybrid-cloud scenario or multiple S3 providers). S3A also can be used
on OBJECT_STORE bucket (although there is a price such as directory markers
mechanism, etc) although but OFS has been restricted to only run on LEGACY and
FSO bucket layouts.
We can write a document to compare these documents and add a link to the base
S3A and OFS documentation.
> [Website v2] [Docs] [User Guide] s3a vs ofs
> -------------------------------------------
>
> Key: HDDS-15380
> URL: https://issues.apache.org/jira/browse/HDDS-15380
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Major
>
> Both S3A and OFS are Hadoop-compatible file system that can be used on Ozone.
> Each protocols have their own use cases and we should document it to inform
> users which protocols would fit their use cases.
> For example, OFS should be faster than S3A since it does not need another
> proxy (i.e. S3G) in the data path. However, S3A can support per-bucket
> configuration (i.e. for hybrid-cloud scenario or multiple S3 providers). S3A
> also can be used on OBJECT_STORE bucket (although there is a price such as
> directory markers mechanism, etc) although but OFS has been restricted to
> only run on LEGACY and FSO bucket layouts.
> We can write a document to compare these documents and add a link to the base
> S3A and OFS documentation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
