[
https://issues.apache.org/jira/browse/HDDS-15089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-15089:
-------------------------------
Parent Issue: HDDS-15207 (was: HDDS-14424)
> Support S3 per request read consistency
> ---------------------------------------
>
> Key: HDDS-15089
> URL: https://issues.apache.org/jira/browse/HDDS-15089
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Major
>
> Since we already supported per request read consistency in OmClientProtocol,
> we can integrate S3G to allow users to pick which consistency they would like
> to use. S3 client can specify "x-ozone-read-consistency" to local-lease to
> pick lower consistency or linearizable-follower for follower read
> consistency. The default read consistency (if unspecified) would be leader
> read so that there is no performance regression.
> Another idea is to also have different follower proxy provider for each
> consistency so that strong read failover proxy provider and local read
> failover proxy provider is separated.
> Similar to Tigris S3:
> https://community.fly.io/t/tigris-consistency-questions/24046/5
> (X-Tigris-Consistent)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
