[
https://issues.apache.org/jira/browse/IGNITE-26619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-26619:
------------------------------------
Description:
* In thin client protocol, explicit read-only transactions propagate
*observableTimestamp*
* However, read operations without an explicit transaction *do not* send
*observableTimestamp*, so implicit RO TX has different behavior
* Inconsistent behavior can be observed when consequent read requests for the
same key go to different nodes. This can happen on connection failure or due to
round-robing in thin client when primary replica connection is not available
was:
* In thin client protocol, explicit read-only transactions propagate
*observableTimestamp*
* However, read operations without an explicit transaction *do not* send
*observableTimestamp*, so implicit RO TX has different behavior
> Implicit client ro tx does not include observableTimestamp
> ----------------------------------------------------------
>
> Key: IGNITE-26619
> URL: https://issues.apache.org/jira/browse/IGNITE-26619
> Project: Ignite
> Issue Type: Bug
> Components: thin clients ai3
> Affects Versions: 3.0
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: ignite-3
> Fix For: 3.1
>
>
> * In thin client protocol, explicit read-only transactions propagate
> *observableTimestamp*
> * However, read operations without an explicit transaction *do not* send
> *observableTimestamp*, so implicit RO TX has different behavior
> * Inconsistent behavior can be observed when consequent read requests for
> the same key go to different nodes. This can happen on connection failure or
> due to round-robing in thin client when primary replica connection is not
> available
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
