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/04/10 14:36:00 UTC

[jira] [Assigned] (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:all-tabpanel ]

Stanislav Lukyanov reassigned IGNITE-7704:
------------------------------------------

    Assignee: Stanislav Lukyanov

> 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
>
> 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)