You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Fedotov (JIRA)" <ji...@apache.org> on 2018/09/16 22:38:00 UTC
[jira] [Comment Edited] (IGNITE-8619) Remote node could not start
in ssh connection
[ https://issues.apache.org/jira/browse/IGNITE-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16616930#comment-16616930 ]
Ivan Fedotov edited comment on IGNITE-8619 at 9/16/18 10:37 PM:
----------------------------------------------------------------
[~ilantukh], In this PR I try to ensure that process of launching remote node via ssh was really started [1]: for this I try to find in output message from command info about new process [2] and set up timeout to exclude hangup of the program [3].
Timeout was already used in channel session [4], so I didn't change value of timeout and put it to separate method.
After that locally failures stopped, but they sometimes appeared on TC. I suggested that there is not enough time for TC to start ssh connection and session closed before it, so I increased amount of attempts in tests to connect via ssh [5] (3 attempts).
[1] [https://github.com/apache/ignite/pull/4314/files#diff-4d335e59ce7e98c67f5d807753829fa7R275]
[2][https://github.com/apache/ignite/pull/4314/files#diff-4d335e59ce7e98c67f5d807753829fa7R353]
[3] [https://github.com/apache/ignite/pull/4314/files#diff-4d335e59ce7e98c67f5d807753829fa7R360]
[4] [https://github.com/apache/ignite/pull/4314/files#diff-4d335e59ce7e98c67f5d807753829fa7R496]
[5] [https://github.com/apache/ignite/pull/4314/files#diff-3de58736d52c13840244c683e4718cc1R633]
was (Author: ivanan.fed):
[~ilantukh], In this PR I try to ensure that process of launching remote node via ssh was really started [1]: for this I try to find in output message from command info about new process [2] and set up timeout to exclude hangup of the program.
Timeout was already used in channel session [4], so I didn't change value of timeout and put it to separate method.
After that locally failures stopped, but they sometimes appeared on TC. I suggested that there is not enough time for TC to start ssh connection and session closed before it, so I increased amount of attempts in tests to connect via ssh [5] (3 attempts).
[1] [https://github.com/apache/ignite/pull/4314/files#diff-4d335e59ce7e98c67f5d807753829fa7R275]
[2][https://github.com/apache/ignite/pull/4314/files#diff-4d335e59ce7e98c67f5d807753829fa7R353]
[3] [https://github.com/apache/ignite/pull/4314/files#diff-4d335e59ce7e98c67f5d807753829fa7R360]
[4] [https://github.com/apache/ignite/pull/4314/files#diff-4d335e59ce7e98c67f5d807753829fa7R496]
[5] [https://github.com/apache/ignite/pull/4314/files#diff-3de58736d52c13840244c683e4718cc1R633]
> 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.7
>
>
> 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)