[
https://issues.apache.org/jira/browse/IGNITE-20553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-20553:
-------------------------------------
Reviewer: Roman Puchkovskiy
> Unexpected rebalancing immediately after table creation
> -------------------------------------------------------
>
> Key: IGNITE-20553
> URL: https://issues.apache.org/jira/browse/IGNITE-20553
> Project: Ignite
> Issue Type: Bug
> Reporter: Kirill Tkalenko
> Assignee: Alexander Lapin
> Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> During the implementation of IGNITE-20330, it was discovered that when
> running
> {*}org.apache.ignite.internal.runner.app.ItDataSchemaSyncTest#checkSchemasCorrectlyRestore{*},
> a situation may occur that after creating the table, rebalancing will begin
> and this test will freeze on the first insert ({*}sql(ignite1,
> String.format("INSERT INTO " + TABLE_NAME + " VALUES(%d, %d, %d)", i, i, 2 *
> i));{*}). The situation is not reproduced often; you need to run the test
> several times.
> h3. Upd#1
> It's a known issue that node restart is broken. Before proceeding with the
> given ticket metastorage compaction epic should be finished, especially
> https://issues.apache.org/jira/browse/IGNITE-20210
> h3. Upd#2
> This ticket should refined in the term of awaiting logical topology be the
> same as on the CMG leader for any node before creating any table
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
