[IGNITE-22500] Remove unnecessary waits when creating an index

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Labels: ignite-3
• Assignee: Ivan Bessonov
• Reporter: Roman Puchkovskiy
• Created: 13/Jun/24 14:01
• Updated: 26/Jun/24 14:54
• Resolved: 26/Jun/24 14:54

Description

When creating an index with current defaults (DelayDuration=1sec, MaxClockSkew=500ms, IdleSafeTimePropagationPeriod=1sec), it takes 6-6.5 seconds on my machine (without concurrent transactions, on an empty table that was just created).

According to the design, we need to first wait for the REGISTERED state to activate on all nodes, including the ones that are currently down; this is to make sure that all transactions started on schema versions before the index creation have finished before we start to build the index (this makes us waiting for DelayDuration+MaxClockSkew). Then, after the build finishes, we switch the index to the AVAILABLE state. This requires another wait of DelayDuration+MaxClockSkew.

Because of IGNITE-20378, in the second case we actually wait longer (for additional IdleSafeTimePropagationPeriod+MaxClockSkew).

The total of waits is thus 1.5+3=4.5sec. But index creation actually takes 6-6.5 seconds. It looks like there are some additional delays (like submitting to the Metastorage and executing its watches).

Issue Links

• is related to: IGNITE-20378 Both clients and embedded nodes should have an ability to see same-actor schema adjustments though RO requests
• is related to: IGNITE-22502 Change default DelayDuration to 500ms