[
https://issues.apache.org/jira/browse/IGNITE-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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&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)
