You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Steshin (Jira)" <ji...@apache.org> on 2021/01/29 10:40:00 UTC
[jira] [Comment Edited] (IGNITE-14096) Try to bring randomization
in node waiting with TcpDiscoverySpi.reconnectDelay.
[ https://issues.apache.org/jira/browse/IGNITE-14096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17274304#comment-17274304 ]
Vladimir Steshin edited comment on IGNITE-14096 at 1/29/21, 10:39 AM:
----------------------------------------------------------------------
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
Logs attached.
[1] https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/tests/discovery_test.py
was (Author: vladsz83):
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
> Attachments: session_log_14096_pr8723.info, session_log_standard.info
>
> Time Spent: 0.5h
> 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)