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

Reply via email to