[jira] [Commented] (IGNITE-18835) Get rid of skipping safe time waiting on a primary node

["Mirza Aliev (Jira)" <ji...@apache.org>]

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

Mirza Aliev commented on IGNITE-18835:
--------------------------------------

[~v.pyatkov] LGTM

> Get rid of skipping safe time waiting on a primary node
> -------------------------------------------------------
>
>                 Key: IGNITE-18835
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18835
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Mirza Aliev
>            Assignee: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Currently, we have a logic of skipping safe time waiting on a primary node in {{PartitionReplicaListener}} for read-only transaction, for example in {{PartitionReplicaListener#processReadOnlySingleEntryAction}}
> {code:java}
>         CompletableFuture<Void> safeReadFuture = isPrimary ? completedFuture(null) : safeTime.waitFor(request.readTimestamp());
>         return safeReadFuture.thenCompose(unused -> resolveRowByPkForReadOnly(searchRow, readTimestamp));
> {code}
> This is a wrong behaviour, we expect that this awaiting must be done on a primary node as well



--
This message was sent by Atlassian Jira
(v8.20.10#820010)