[jira] [Commented] (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=16681139#comment-16681139 ] ASF GitHub Bot commented on IGNITE-8619: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4314 > 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=6814497542781613621=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)
[jira] [Commented] (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=16627017#comment-16627017 ] Ivan Fedotov commented on IGNITE-8619: -- [~dpavlov] I rerun tests. It remains only one "possible blocker" [.NET inspections|https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll==pull%2F4314%2Fhead=Latest], I tried to rerun it several times, but when I looked in the history of this test, it becomes clear that [master|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformNetInspections=buildTypeHistoryList_IgniteTests24Java8=%3Cdefault%3E] also has such problem in the recent 6 runs. So I think that now there are no possible blockers according this ticket. > 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=6814497542781613621=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)
[jira] [Commented] (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=16625839#comment-16625839 ] Dmitriy Pavlov commented on IGNITE-8619: [~ivanan.fed] [~SomeFire] it may be unrelated failure, so rerun of one suite may be perfectly ok > 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=6814497542781613621=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)
[jira] [Commented] (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=16625784#comment-16625784 ] Ryabov Dmitrii commented on IGNITE-8619: [~ivanan.fed], please, fix the test and rerun tests. > 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=6814497542781613621=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)
[jira] [Commented] (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=16625773#comment-16625773
]
Ignite TC Bot commented on IGNITE-8619:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1923569]]
* IgnitePdsWithIndexingCoreTestSuite:
IgnitePdsDiskErrorsRecoveringTest.testRecoveringOnNodeStartMarkerWriteFail -
0,0% fails in last 100 master runs.
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=1923608buildTypeId=IgniteTests24Java8_RunAll]
> 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=6814497542781613621=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)
[jira] [Commented] (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=16625696#comment-16625696 ] Dmitriy Pavlov commented on IGNITE-8619: [~ivanan.fed] could you please check your PR runs and trigger bot to comment this issue? > 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=6814497542781613621=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)
[jira] [Commented] (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=16625652#comment-16625652 ] Ivan Fedotov commented on IGNITE-8619: -- [~dpavlov], could you look at this PR, please? > 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=6814497542781613621=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)
[jira] [Commented] (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=16625576#comment-16625576 ] Ivan Fedotov commented on IGNITE-8619: -- [~oignatenko], I agree with you: now I also tend to think that it's infrastructure issue at Teamcity. In this way I move status of this ticket to PA. > 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=6814497542781613621=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)
[jira] [Commented] (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=16625253#comment-16625253 ] Oleg Ignatenko commented on IGNITE-8619: [~ivanan.fed] yeah I also noticed that tests are not yet 100% stable when I tried them on Teamcity. I preferred simpler version (without additional connection attempts) only because at this point there seem to be not enough evidence that this will really fix things (as I wrote before, there is a chance that reason of failures is some infrastructure issue at Teamcity that we haven't yet discovered). I still feel that at this point it is too early to add additional connection attempts in tests. However I do not insist on that and if you believe that it is really necessary I will be fine if you add these. > 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=6814497542781613621=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)
[jira] [Commented] (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=16625215#comment-16625215 ] Ivan Fedotov commented on IGNITE-8619: -- [~oignatenko], I run tests [again|https://ci.ignite.apache.org/viewLog.html?buildId=1923543=buildResultsDiv=IgniteTests24Java8_StartNodes] and it were several failures because of ``Remote node could not star``. So I think that it's necessary to return additional [attempts|https://github.com/apache/ignite/pull/4314/commits/a79160436eff732b6d880c92679271f3a9605006#diff-3de58736d52c13840244c683e4718cc1R854] of connecting via ssh in the tests. > 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=6814497542781613621=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)
[jira] [Commented] (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=16623348#comment-16623348
]
Oleg Ignatenko commented on IGNITE-8619:
[~ivanan.fed] understood - I checked your latest commit {{ae5654a}} and it
addresses all my concerns, thank you. Confirm my prior recommendation to merge
this into master
> 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=6814497542781613621=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)
[jira] [Commented] (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=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=6814497542781613621=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)
[jira] [Commented] (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=16621980#comment-16621980
]
Oleg Ignatenko commented on IGNITE-8619:
[~ivanan.fed] I re-checked [most recent revisions at
Github|https://github.com/1vanan/ignite/tree/IGNITE-8619] and these look OK
except for few relatively minor issues in
[IgniteProjectionStartStopRestartSelfTest|https://github.com/1vanan/ignite/blob/IGNITE-8619/modules/ssh/src/test/java/org/apache/ignite/internal/IgniteProjectionStartStopRestartSelfTest.java]:
1) there is one unused import 2) first 6 lines in {{startCheckNodes()}} method
are incorrectly indented and 3) Intellij recommends to inline two last
parameters in {{startNodes}} method because these are always the same.
After above issues are addressed, strongly recommend to merge to master. (cc
[~NSAmelchev])
> 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=6814497542781613621=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)
[jira] [Commented] (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=16620697#comment-16620697
]
Oleg Ignatenko commented on IGNITE-8619:
Proposed changes to {{StartNodeCallableImpl}} look right to me; besides usual
run at Teamcity I also checked them in a customised stress test at my machine
and results were satisfying. Changes made in tests look somewhat troublesome
though - I made some suggestions on that in Upsource. I also would want to see
note from Ilya Lantukh at Upsource resolved (the one where he suggests to add
comment in the source code explaining the regex value passed in parameter).
After my concerns regarding test are resolved, recommend to merge into master.
[~NSAmelchev] - pinging you about this as promised, please feel free to contact
me if needed.
> 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=6814497542781613621=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)
[jira] [Commented] (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=16617419#comment-16617419 ] Ilya Lantukh commented on IGNITE-8619: -- [~ivanan.fed], thanks for detailed explanation, but by "add comments" I meant comments in the source code, not in Jira. > 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=6814497542781613621=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)
[jira] [Commented] (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=16616930#comment-16616930 ] Ivan Fedotov commented on IGNITE-8619: -- [~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=6814497542781613621=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)
[jira] [Commented] (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=16609360#comment-16609360 ] Ilya Lantukh commented on IGNITE-8619: -- [~ivanan.fed], I've reviewed your PR from a Java developer perspective. It's not obvious how and why your solution fixes the problem, please refactor it to be more self-explanatory or add comments. > 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=6814497542781613621=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)
[jira] [Commented] (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=16604191#comment-16604191 ] Peter Ivanov commented on IGNITE-8619: -- [~daradurvs], I am no Java developer, sorry. > 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=6814497542781613621=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)
[jira] [Commented] (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=16602357#comment-16602357 ] Vyacheslav Daradur commented on IGNITE-8619: Hi, [~dpavlov], [~vveider], could you review the solution, please? > 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=6814497542781613621=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)
[jira] [Commented] (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=16590046#comment-16590046 ] Amelchev Nikita commented on IGNITE-8619: - [~ivanan.fed], Looks good to me. > 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 >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > Labels: MakeTeamcityGreenAgain > > 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=6814497542781613621=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)
[jira] [Commented] (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=16533636#comment-16533636 ] ASF GitHub Bot commented on IGNITE-8619: GitHub user 1vanan opened a pull request: https://github.com/apache/ignite/pull/4314 IGNITE-8619 Remote node could not start in ssh connection You can merge this pull request into a Git repository by running: $ git pull https://github.com/1vanan/ignite IGNITE-8619 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4314.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4314 commit e9e9e4ae5c1b31d9218865981cc3a936c6e922b8 Author: Fedotov Date: 2018-07-05T09:36:31Z change shell command commit b90c9cbde31eb8cfd522c7159d1d8c855e4f8904 Author: Fedotov Date: 2018-07-05T11:58:13Z fix shell command > 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 >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > > 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=6814497542781613621=testDetails]. > > So it's necessary to make launch remote node via ssh always succesful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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=16531559#comment-16531559 ] Ivan Fedotov commented on IGNITE-8619: -- [~ein], Hi! I saw your code in StartNodeCallableImpl class and have some questions about it. It will be great, if you help me with them. # Why do you use shell channel [1] to start node and not exec channel [2]? # Why do you insert sleep in shell execution [3]? As I see, autoflush is available. [1][https://github.com/apache/ignite/blob/master/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L309] [2][https://github.com/apache/ignite/blob/master/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L393] [3][https://github.com/apache/ignite/blob/master/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L320] > '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 >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > > 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=6814497542781613621=testDetails]. > > So it's necessary to make launch remote node via ssh always succesful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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=16527434#comment-16527434 ] Peter Ivanov commented on IGNITE-8619: -- [~ivanan.fed], then if ssh connection is made from Java code with JSch API -- how can configuration of SSH server with .sshd will help, especially on Windows environment? May be the code which serves as SSH Daemon can be configured to hold the connection properly? > '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 >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > > 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=6814497542781613621=testDetails]. > > So it's necessary to make launch remote node via ssh always succesful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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=16527375#comment-16527375 ] Ivan Fedotov commented on IGNITE-8619: -- [~vveider], as I understood process of the start node: # We connect to remote node in java via ssh with [JSch|https://github.com/apache/ignite/blob/master/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L128] API in Java. For this we create session with determined username, host, port and password # We [create|https://github.com/apache/ignite/blob/master/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L313] shell channel on this Session object to transfer command which launches Ignite on this node via ignite.sh. After that we wait for 1000 milliseconds until node launches. So we connect via ssh with Java and launch node via shell script. > '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 >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > > 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=6814497542781613621=testDetails]. > > So it's necessary to make launch remote node via ssh always succesful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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=16527358#comment-16527358
]
Peter Ivanov commented on IGNITE-8619:
--
[~ivanan.fed], I still do not see where is {{ssh}} executable in provided
string. Is it called somewhere in {{ignite.sh}} by passing
{{-DIGNITE_SSH_HOST="127.0.0.1"}} parameter?
> '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
>Reporter: Ivan Fedotov
>Assignee: Ivan Fedotov
>Priority: Major
>
> 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=6814497542781613621=testDetails].
>
> So it's necessary to make launch remote node via ssh always succesful.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (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=16527331#comment-16527331 ] Ivan Fedotov commented on IGNITE-8619: -- [~vveider], yes, constructed command is provided below. I launch ssh on local host on Mac OS: *nohup "./ignite/bin/ignite.sh" -v "modules/core/src/test/config/spring-start-nodes.xml" -J-DIGNITE_SSH_HOST="127.0.0.1" -J-DIGNITE_SSH_USER_NAME="ivanan" > /var/folders/k9/gl73xsmn68q0dr12hwhfxtdrgn/T//ignite-startNodes/06-29-2018--11-23-15-746e9b76.log 2>& 1 &* > '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 >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > > 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=6814497542781613621=testDetails]. > > So it's necessary to make launch remote node via ssh always succesful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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=16526445#comment-16526445 ] Peter Ivanov commented on IGNITE-8619: -- [~ivanan.fed], I'm sorry I'm not good at Java. Can you show what exact command is constructed [here|https://github.com/apache/ignite/blob/219bc81b730ea3ba078b61f96c9dab354496c22b/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L257]? > '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 >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > > 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=6814497542781613621=testDetails]. > > So it's necessary to make launch remote node via ssh always succesful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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=16526418#comment-16526418 ] Ivan Fedotov commented on IGNITE-8619: -- [~vveider], I tested locally several hundred times and tests were green until ssh disconnected per timeout, so I made a conclusion that problem may be with TC enviroment. I think that we can be on 100% sure or not, when we change timeout on one agent and run test on this agent on TC for several hundred times. P.S. Remote node starts via shell command in StartNodeCallableImpl class [1]. [1]https://github.com/apache/ignite/blob/master/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L269 > '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 >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > > 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=6814497542781613621=testDetails]. > > So it's necessary to make launch remote node via ssh always succesful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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=16525200#comment-16525200 ] ASF GitHub Bot commented on IGNITE-8619: GitHub user 1vanan opened a pull request: https://github.com/apache/ignite/pull/4268 IGNITE-8619 Failing testClientAtomicLongCreateCloseFailover You can merge this pull request into a Git repository by running: $ git pull https://github.com/1vanan/ignite IGNITE-8619 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4268.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4268 commit f85eb93181128c0cdc02babe06fb7b946819140d Author: Fedotov Date: 2018-06-27T15:22:41Z catch IgniteNeedReconnectException > '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 >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > > 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=6814497542781613621=testDetails]. > > So it's necessary to make launch remote node via ssh always succesful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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=16524876#comment-16524876 ] Peter Ivanov commented on IGNITE-8619: -- [~ivanan.fed], do you have solid proof of ssh timeout cause of the problem. I would not like to update ssh configuration in 100 agent instances not being 100% sure. Also -- ho do you start remote node via ssh? Via shell command, Java code os something else? > '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 >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > > 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=6814497542781613621=testDetails]. > > So it's necessary to make launch remote node via ssh always succesful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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=16524865#comment-16524865 ] Dmitriy Pavlov commented on IGNITE-8619: [~vveider], could you please check if we should set ssh timeout in config or somewhere in maven? ^ > '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 >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > > 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=6814497542781613621=testDetails]. > > So it's necessary to make launch remote node via ssh always succesful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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=16518083#comment-16518083 ] Ivan Fedotov commented on IGNITE-8619: -- [~dpavlov], [~ein], Hi! I investigated this issue and found that locally tests failed only when ssh disconnected per timeout. I assume that ssh timeout on TeamCity could be set incorrectly: as one of StartStopNodes test is started, ssh could be disconnected per timeout. Change ssh timeout on server side is easy, we should add some lines in ~/.ssh/sshd_config file: ClientAliveInternal n - the server send the clients «null packet» every n seconds to keep connection alive, ClientAliveCountMax m - «null packet» will be send m times. I suppose that it can fix flucky tests on ssh connection. What do you think? > '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 >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > > 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=6814497542781613621=testDetails]. > > So it's necessary to make launch remote node via ssh always succesful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
