[
https://issues.apache.org/jira/browse/IGNITE-14095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17274296#comment-17274296
]
Vladimir Steshin commented on IGNITE-14095:
-------------------------------------------
Typical timers to clean and start cluster of 44 nodes on the Discovery ducktape
test [1]: 110-129s:
'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)': 112.0
'Ignite cluster start time (s)': 129.1
'Ignite cluster start time (s)': 127.8
With this PR:
<property name="reconnectDelay" value="160"/>
it shows same results:
'Ignite cluster start time (s)': 128.0
'Ignite cluster start time (s)': 111.8
'Ignite cluster start time (s)': 127.7
'Ignite cluster start time (s)': 110.6
'Ignite cluster start time (s)': 128.3
[1]
https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/tests/discovery_test.py
> Try to fasten cluster start in the ducktests with decreasing
> 'spi.reconnectDelay'
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-14095
> URL: https://issues.apache.org/jira/browse/IGNITE-14095
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladimir Steshin
> Assignee: Vladimir Steshin
> Priority: Minor
> Time Spent: 10m
>
> Try to speed up cluster start ath the ducktests with decreasing
> TcpDiscoverySpi.reconnectDelay
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
