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/07/04 13:42: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=16532766#comment-16532766 ]
Stanislav Lukyanov commented on IGNITE-7704:
--------------------------------------------
Attached a new version of the doc update draft (timeouts_v2.md): added description of metricsUpdateFrequency and described relations of failureDetectionTimeout, clientFailureDetectionTimeout and metrucsUpdateFrequency.
> 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, 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
(v7.6.3#76005)