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

Posted to issues@ignite.apache.org by "Aleksandr Polovtsev (Jira)" <ji...@apache.org> on 2025/02/14 09:39:00 UTC

[jira] [Updated] (IGNITE-24525) Fix races during table removal and Raft snapshots

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

Aleksandr Polovtsev updated IGNITE-24525:
-----------------------------------------
    Description: 
When a Raft snapshot is taken over a Zone Raft group, we have a bunch of table storages that will participate in this snapshot. However, the set of these storages can change, because new tables can be removed from the zone concurrently. We need to introduce proper synchronization, so that new storages do not interfere with creating a snapshot or application of a snapshot and cover it with tests.

Note that unlike the table creation scenario (IGNITE-24522) this affects both the sending and the receiving side.

  was:
When a Raft snapshot is taken over a Zone Raft group, we have a bunch of table storages that will participate in this snapshot. However, the set of these storages can change, because new tables can be removed from the zone concurrently. We need to introduce proper synchronization, so that new storages do not interfere with creating a snapshot or application of a snapshot and cover it with tests.

Note that unlike the table creation scenario (


> Fix races during table removal and Raft snapshots
> -------------------------------------------------
>
>                 Key: IGNITE-24525
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24525
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Aleksandr Polovtsev
>            Assignee: Aleksandr Polovtsev
>            Priority: Major
>              Labels: ignite-3
>
> When a Raft snapshot is taken over a Zone Raft group, we have a bunch of table storages that will participate in this snapshot. However, the set of these storages can change, because new tables can be removed from the zone concurrently. We need to introduce proper synchronization, so that new storages do not interfere with creating a snapshot or application of a snapshot and cover it with tests.
> Note that unlike the table creation scenario (IGNITE-24522) this affects both the sending and the receiving side.



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