You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Andrew Medvedev (JIRA)" <ji...@apache.org> on 2018/05/20 22:04:00 UTC
[jira] [Created] (IGNITE-8533) Timeout collision in Client Nodes
test suite
Andrew Medvedev created IGNITE-8533:
---------------------------------------
Summary: Timeout collision in Client Nodes test suite
Key: IGNITE-8533
URL: https://issues.apache.org/jira/browse/IGNITE-8533
Project: Ignite
Issue Type: Bug
Reporter: Andrew Medvedev
Fix For: 2.6
IGNITE-8085 increased NODE_START_CHECK_LIMIT so "remote" node log is parsed for longer (set now to 25 * 2000ms)
https://github.com/apache/ignite/blob/fe6e70e3c8d6a6349ea00b7ec99b215945ffce6d/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L85
This exceeds total timeout set up for remote node startup in
[https://github.com/apache/ignite/blob/282b334f76479460613f28347d8cea97ba23f795/modules/ssh/src/test/java/org/apache/ignite/internal/IgniteProjectionStartStopRestartSelfTest.java#L1054] (40 * 1000ms)
This leads to debug message with ref to remote log file being never shown because 50000 timeout will never be reached
[https://github.com/apache/ignite/blob/fe6e70e3c8d6a6349ea00b7ec99b215945ffce6d/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L285]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)