[ https://issues.apache.org/jira/browse/IGNITE-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16623336#comment-16623336 ]
Ivan Fedotov commented on IGNITE-8619: -------------------------------------- [~oignatenko], thank you for notation, method ```testStartThreeNodes()``` in master has another timeout and max connection [params|https://github.com/apache/ignite/blob/master/modules/ssh/src/test/java/org/apache/ignite/internal/IgniteProjectionStartStopRestartSelfTest.java#L243], so I change it (according to this it becomes necessary to remain two last parameters in {{startNodes)}}. Second notation is also included in the new commit. > Remote node could not start in ssh connection > --------------------------------------------- > > Key: IGNITE-8619 > URL: https://issues.apache.org/jira/browse/IGNITE-8619 > Project: Ignite > Issue Type: Bug > Affects Versions: 2.6 > Reporter: Ivan Fedotov > Assignee: Ivan Fedotov > Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > Now there is a problem with launch remote node via ssh. Initially was an > assumption that it's due to remote process has not enough time to write > information into log: > [IGNITE-8085|https://issues.apache.org/jira/browse/IGNITE-8085]. But this > correction didn't fix [TeamCity > |https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=6814497542781613621&tab=testDetails] > (IgniteProjectionStartStopRestartSelfTest.testStartFiveNodesInTwoCalls). > So it's necessary to make launch remote node via ssh always succesful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)