Kirill Tkalenko created IGNITE-22656:
----------------------------------------
Summary: Don't fire PrimaryReplicaEvent#PRIMARY_REPLICA_ELECTED
for destroyed tables by LWM
Key: IGNITE-22656
URL: https://issues.apache.org/jira/browse/IGNITE-22656
Project: Ignite
Issue Type: Bug
Reporter: Kirill Tkalenko
If you increase the number of replicas in default zone to 5, random integration
tests will start to fail with
*org.apache.ignite.internal.lang.IgniteInternalException: Table storage for the
specified table cannot be null*.
To reproduce the issue change
*org.apache.ignite.internal.catalog.commands.CatalogUtils#DEFAULT_REPLICA_COUNT*
and run *org.apache.ignite.internal.sql.sqllogic.ItSqlLogicTest*.
Occurs because
*org.apache.ignite.internal.placementdriver.event.PrimaryReplicaEvent#PRIMARY_REPLICA_ELECTED*
is fired after the table is removed from the catalog and destroyed by LWM.
For me, this event should not have been generated anymore for destroyed table.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
