You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/21 13:24: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=16956075#comment-16956075 ]
Maxim Muzafarov commented on IGNITE-7704:
-----------------------------------------
[~slukyanov]
Hello, what should be the next steps to resolve this issue?
> 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
> Fix For: 2.8
>
> Attachments: timeouts.md, timeouts_v2.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
(v8.3.4#803005)