You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexey Scherbakov (Jira)" <ji...@apache.org> on 2024/12/27 13:49:00 UTC

[jira] [Updated] (IGNITE-24132) Consider removing of storageIndexTracker

     [ https://issues.apache.org/jira/browse/IGNITE-24132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Scherbakov updated IGNITE-24132:
---------------------------------------
    Description: 
Currently storageIndexTracker is used to wait for up to date primary replica state.

But we already have [1] which can be used for the same purpose:

1. trigger safe time sync command

2. wait for it's safe time.

[1] org.apache.ignite.internal.table.distributed.raft.PartitionListener#safeTimeTracker

  was:
Currently storageIndexTracker is used to wait for up to date primary replica state.

But we already have org.apache.ignite.internal.table.distributed.raft.PartitionListener#safeTimeTracker

which can be used for the same purpose.


> Consider removing of storageIndexTracker
> ----------------------------------------
>
>                 Key: IGNITE-24132
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24132
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexey Scherbakov
>            Priority: Major
>              Labels: ignite-3
>
> Currently storageIndexTracker is used to wait for up to date primary replica state.
> But we already have [1] which can be used for the same purpose:
> 1. trigger safe time sync command
> 2. wait for it's safe time.
> [1] org.apache.ignite.internal.table.distributed.raft.PartitionListener#safeTimeTracker



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