You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Stanislav Lukyanov (JIRA)" <ji...@apache.org> on 2018/05/28 20:21:00 UTC

[jira] [Commented] (IGNITE-7704) Document IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations

    [ https://issues.apache.org/jira/browse/IGNITE-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492911#comment-16492911 ] 

Stanislav Lukyanov commented on IGNITE-7704:
--------------------------------------------

Attached a doc update draft (timeouts.md).

> Document IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations
> -----------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-7704
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7704
>             Project: Ignite
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 2.3
>            Reporter: Alexey Popov
>            Assignee: Stanislav Lukyanov
>            Priority: Major
>         Attachments: timeouts.md
>
>
> We often see similar questions related to IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations. And we see several side-effects after incorrect timeout configuration.
> It looks like this question is not well documented.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)