[
https://issues.apache.org/jira/browse/IGNITE-24540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17935483#comment-17935483
]
Vladislav Pyatkov commented on IGNITE-24540:
--------------------------------------------
I looked in the log and found too many rows about issues with leases. They
started from:
{noformat}
2025-02-16 02:58:43:568 +0000
[WARNING][%TablesAmountCapacityMultiNodeTest_cluster_1%JRaft-FSMCaller-Disruptormetastorage_stripe_0-0][LeaseUpdater]
Lease update invocation failed because of outdated lease data on this node.
{noformat}
Littele bit after we got an exception (SQLException), that posted in the
description. It means the metastorage does not update leases for a long time.
So I think the root cause was described and fixed in IGNITE-24790.
[~vdmitrienko] Could you please check this test again in the new build?
> Creating 1000 tables with 200 columns throws "The primary replica has changed"
> ------------------------------------------------------------------------------
>
> Key: IGNITE-24540
> URL: https://issues.apache.org/jira/browse/IGNITE-24540
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Affects Versions: 3.0, 3.0.0-beta1
> Environment: 3 nodes (each node is CMG, each node
> {color:#067d17}"-Xms4096m"{color}, {color:#067d17}"-Xmx4096m"{color}), each
> on separate host. Each host vCPU: 4, Memory: 32GB.
> Reporter: Vladimir Dmitrienko
> Priority: Major
> Labels: ignite-3
> Attachments: node_1_logs.zip, node_2_logs.zip, node_3_logs.zip,
> test.log
>
>
> *Steps to reproduce:*
> # Start 3 nodes (each node is CMG, each node
> {color:#067d17}"-Xms4096m"{color}, {color:#067d17}"-Xmx4096m"{color}), each
> on separate host. Each host vCPU: 4, Memory: 32GB.
> # Create 50 tables with 200 columns in 1 thread.
> # Assert 50 tables are present in system view.
> # Insert 1 row into each.
> # Assert rows content is correct.
> # Repeat steps 2-5 while amount of tables is 1000.
> *Expected:*
> 1000 tables are created.
> *Actual:*
> Exception during 400 - 449 tables creation at step 5.
> {code:java}
> java.sql.SQLException:
> The primary replica has changed [
> expectedLeaseholderName=TablesAmountCapacityMultiNodeTest_cluster_2,
> currentLeaseholderName=null,
> expectedLeaseholderId=1522cfcd-0400-4d23-9015-31dfbad90780,
> currentLeaseholderId=null,
> expectedEnlistmentConsistencyToken=114017056457556334,
> currentEnlistmentConsistencyToken=null
> ]{code}
> Based on the information in the exception, it appears to have been thrown
> from the {{PartitionReplicaListener#ensureReplicaIsPrimary}} method.
> *Notes:*
> The issue might be related to:
> https://issues.apache.org/jira/browse/IGNITE-20911
--
This message was sent by Atlassian Jira
(v8.20.10#820010)