[
https://issues.apache.org/jira/browse/IGNITE-16033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453051#comment-17453051
]
Alexander Lapin commented on IGNITE-16033:
------------------------------------------
[~v.pyatkov] LGTM
> Wrong completion of an alter table operation for a slowing node
> ---------------------------------------------------------------
>
> Key: IGNITE-16033
> URL: https://issues.apache.org/jira/browse/IGNITE-16033
> Project: Ignite
> Issue Type: Bug
> Reporter: Kirill Tkalenko
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Two nodes send a request to change the table (for example, adding the column
> "column1"), if one of the nodes slowed down (could not update the
> configuration in the metastorage due to the network), then one of the nodes
> will be able to perform the operation (the column will be added), and the
> second, after returning to the cluster there will be no error to perform the
> operation, since when a new configuration is received from the metastorrage,
> a notification about a schema change will occur, which will complete all
> current operations to change the table, although there should be an error
> (the column already exists). In fact, the error will be later, but she will
> not be able to complete the operation with it because the operation was
> completed on notification of a change in the table configuration.
> Tests:
> *
> *org.apache.ignite.internal.runner.app.ItTablesApiTest#testAddColumnFromLaggedNode*;
> *
> *org.apache.ignite.internal.runner.app.ItTablesApiTest#testAddIndexFromLaggedNode*.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
