[
https://issues.apache.org/jira/browse/IGNITE-29100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Davydov updated IGNITE-29100:
------------------------------------
Epic Link: IGNITE-26208
> Document TcpDiscoverySpi.networkTimeout for multi data center deployments
> -------------------------------------------------------------------------
>
> Key: IGNITE-29100
> URL: https://issues.apache.org/jira/browse/IGNITE-29100
> Project: Ignite
> Issue Type: Test
> Reporter: Maksim Davydov
> Assignee: Maksim Davydov
> Priority: Minor
> Labels: IEP-140, ise
>
> In a cluster that spans data centers, a joining node waits for its join to
> complete for `TcpDiscoverySpi.networkTimeout` (5 seconds by default). The
> join has to pass the whole discovery ring, so with a long round trip between
> data centers it can take longer, and the node then repeats its join while the
> rest of the cluster is already waiting for it in partition map exchange.
> The setting is separate from `IgniteConfiguration.networkTimeout`, and the
> documentation does not say so. This adds a note to the Multi Data Center page
> and clarifies the `networkTimeout` row of the discovery properties table.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
