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

Posted to issues@ignite.apache.org by " Kirill Sizov (Jira)" <ji...@apache.org> on 2024/12/20 14:13:00 UTC

[jira] [Commented] (IGNITE-23937) WriteIntentSwitchReplicaRequest handling misses schema sync

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

 Kirill Sizov commented on IGNITE-23937:
----------------------------------------

[~rpuch] to review and update this task.

> WriteIntentSwitchReplicaRequest handling misses schema sync
> -----------------------------------------------------------
>
>                 Key: IGNITE-23937
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23937
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Roman Puchkovskiy
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>
> In PartitionReplicaListener, when handling WriteIntentSwitchReplicaRequests, we don't do schema sync at the corresponding transaction begin ts, so, when we try to access indices to remove writes from them for an aborting  WriteIntentSwitchReplicaRequest, we might see a stale Catalog and fail to get indices for the table if the table is already dropped.
> Apart from fixing this, we should probably also
>  * Make sure that all request types are added to tests in PartitionReplicaListenerTest that verify schema sync
>  * Rearrange the code to make it more difficult to miss application of schema sync when adding a new request type



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