You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Stanilovsky Evgeny (JIRA)" <ji...@apache.org> on 2019/03/18 10:57:00 UTC
[jira] [Commented] (IGNITE-11427) Document custom node fail
functional.
[ https://issues.apache.org/jira/browse/IGNITE-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794925#comment-16794925 ]
Stanilovsky Evgeny commented on IGNITE-11427:
---------------------------------------------
excludeNode: will initiate failure of provided node, in case of Server node - it will be SEGMENTED (replaced from topology), for Client node it would be replaced from topology but if [1] option: TcpDiscoverySpi#setClientReconnectDisabled not disabled, it would reconnect once more after timeout.
[1] https://apacheignite.readme.io/docs/clients-vs-servers#reconnecting-a-client
> Document custom node fail functional.
> -------------------------------------
>
> Key: IGNITE-11427
> URL: https://issues.apache.org/jira/browse/IGNITE-11427
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 2.7
> Reporter: Stanilovsky Evgeny
> Priority: Major
> Fix For: 2.8
>
> Attachments: Screenshot_20190227_100539.png
>
>
> Append additional node fail documentation related to [1]
> [1] https://issues.apache.org/jira/browse/IGNITE-11332
>
> how it looks into jconsole:
> !Screenshot_20190227_100539.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)