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