[
https://issues.apache.org/jira/browse/IGNITE-14096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17274304#comment-17274304
]
Vladimir Steshin commented on IGNITE-14096:
-------------------------------------------
Typical timers to clean and start cluster of 44 nodes on the Discovery ducktape
test [1]: 111-129s (for dev. and 2.9.0 versions)
'Ignite cluster start time (s)': 129.5
'Ignite cluster start time (s)': 112.2
'Ignite cluster start time (s)': 128.6
'Ignite cluster start time (s)': 129.1
'Ignite cluster start time (s)': 112.0
'Ignite cluster start time (s)': 111.4
With this PR it shows same results:
'Ignite cluster start time (s)': 128.8
'Ignite cluster start time (s)': 112.9
'Ignite cluster start time (s)': 129.0
'Ignite cluster start time (s)': 112.5
[1]
https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/tests/discovery_test.py
> Try to bring randomization in node waiting with
> TcpDiscoverySpi.reconnectDelay.
> -------------------------------------------------------------------------------
>
> Key: IGNITE-14096
> URL: https://issues.apache.org/jira/browse/IGNITE-14096
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladimir Steshin
> Assignee: Vladimir Steshin
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> To speed up cluster start slyghtly, try to bring randomization in node
> waiting with TcpDiscoverySpi.reconnectDelay. Check with the ducktape
> integration tests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
