[
https://issues.apache.org/jira/browse/IGNITE-8657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503093#comment-16503093
]
Sergey Chugunov commented on IGNITE-8657:
-----------------------------------------
Patch artifacts: [PR|https://github.com/apache/ignite/pull/4102],
[TC|https://ci.ignite.apache.org/viewLog.html?buildId=1359981&;],
[review|https://reviews.ignite.apache.org/ignite/review/IGNT-CR-633]
> Simultaneous start of bunch of client nodes may lead to some clients hangs
> --------------------------------------------------------------------------
>
> Key: IGNITE-8657
> URL: https://issues.apache.org/jira/browse/IGNITE-8657
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Sergey Chugunov
> Assignee: Sergey Chugunov
> Priority: Major
> Fix For: 2.6
>
>
> h3. Description
> PartitionExchangeManager uses a system property
> *IGNITE_EXCHANGE_HISTORY_SIZE* to manage max number of exchange objects and
> optimize memory consumption.
> Default value of the property is 1000 but in scenarios with many caches and
> partitions it is reasonable to set exchange history size to a smaller values
> around few dozens.
> Then if user starts up at once more client nodes than history size some
> clients may hang because their exchange information was preempted and no
> longer available.
> h3. Workarounds
> Two workarounds are possible:
> * Do not start at once more clients than history size.
> * Restart hanging client node.
> h3. Solution
> Forcing client node to reconnect when server detected loosing its exchange
> information prevents client nodes hanging.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
