You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2025/11/20 10:32:00 UTC

[jira] [Commented] (IGNITE-26619) Implicit client ro tx does not include observableTimestamp

    [ https://issues.apache.org/jira/browse/IGNITE-26619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039589#comment-18039589 ] 

Pavel Tupitsyn commented on IGNITE-26619:
-----------------------------------------

Maybe there is no problem. The failure from IGNITE-26495 is not fixed by using a single connection, so it is something unrelated.

> 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: Critical
>              Labels: ignite-3
>             Fix For: 3.2
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> * 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)