[
https://issues.apache.org/jira/browse/HDDS-14509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-14509:
-------------------------------
Description:
Currently, if OM follower read is enabled, all OM followers will serve read
requests even if the client does not enable the follower read.
For read-only client, this might be unexpected since they expect the OM
follower to throw OMNotLeaderException.
We can support some kind of OM request metadata to indicate to the OM whether
the client enables the follower read or not. This can be initial implementation
of configurable client read consistency. Currently we will support LEADER_ONLY,
LINEARIZABLE, STALE_BOUNDED_READS with follower index lag specified (in the
future we can add another field for the timestamp-based staleness bound once it
is supported).
was:
Currently, if OM follower read is enabled, all OM followers will serve read
requests even if the client does not enable the follower read.
For read-only client, this might be unexpected since they expect the OM
follower to throw OMNotLeaderException.
We can support some kind of OM request metadata to indicate to the OM whether
the client enables the follower read or not. This can be initial implementation
of configurable client read consistency. Currently we will support LEADER_ONLY,
LINEARIZABLE, STALE_BOUNDED_READS with follower index lag specified.
> Allow client to choose the read consistency level
> -------------------------------------------------
>
> Key: HDDS-14509
> URL: https://issues.apache.org/jira/browse/HDDS-14509
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Major
>
> Currently, if OM follower read is enabled, all OM followers will serve read
> requests even if the client does not enable the follower read.
> For read-only client, this might be unexpected since they expect the OM
> follower to throw OMNotLeaderException.
> We can support some kind of OM request metadata to indicate to the OM whether
> the client enables the follower read or not. This can be initial
> implementation of configurable client read consistency. Currently we will
> support LEADER_ONLY, LINEARIZABLE, STALE_BOUNDED_READS with follower index
> lag specified (in the future we can add another field for the timestamp-based
> staleness bound once it is supported).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
