Mirza Aliev created IGNITE-18835:
------------------------------------
Summary: 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
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)