[IGNITE-16760] Performance degradation of IgniteTables#tables after configuration changes

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha4
• Fix Version/s: 3.0.0-beta1
• Labels: fix-version-validated ignite-3
• Assignee: Denis Chudov
• Reporter: Taras Ledkov
• Reviewer: Alexander Lapin
• Created: 29/Mar/22 11:53
• Updated: 01/Nov/22 11:07
• Resolved: 04/Jul/22 22:19

Description

Performance degradation of configuration changes:
Steps to reproduce:
1. Start cluster with 3 nodes
2. Run in the loop

CREATE TABLE TEST(ID INTEGER PRIMARY KEY, V INTEGER)
for (Table t : ign.tables().tables()) {
    <DROP TABLE  t.name()>;
}

On begin IgniteTables#tables takes ~ 0.7 sec.
The time of the operation is grown.
The time after ~100 iteration is about 20 sec.

Issue Links

• is related to: IGNITE-17278 TableManager#directTableIds can't be implemented effectively
• is related to: IGNITE-17291 Implement metastorage cursor batching
• links to: GitHub Pull Request #918
• links to: PR