[
https://issues.apache.org/jira/browse/IGNITE-24703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-24703:
--------------------------------------
Fix Version/s: 3.1
> Sql. Wait for system views to complete registration on node start/join
> ----------------------------------------------------------------------
>
> Key: IGNITE-24703
> URL: https://issues.apache.org/jira/browse/IGNITE-24703
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Pavel Pereslegin
> Assignee: Andrey Mashenkov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, when a node starts, we do not wait for the completion of catalog
> command which creates/replaces system views.
> See {{SystemViewManagerImpl}}
> {code:Java}
> public CompletableFuture<Void> completeRegistration
> {code}
> Initially, we waited for this future to complete at the node start, but this
> noteceably increased the test execution time (by about 10%). And at that
> moment we decided to remove this delay.
> As a result, any integration test that accesses system views is now forced to
> wait this future separately.
> {code:java}
> @BeforeAll
> protected void awaitSystemViewRegistration() {
> await(systemViewManager().completeRegistration());
> }
> {code}
> It is necessary to repeat the attempt to add a wait when starting (or
> joining) a node and check whether there is a slowdown in the execution of
> integration tests. If it is insignificant, then leave this condition when
> starting the node and remove it from the tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
