You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/05/31 15:51:00 UTC
[jira] [Commented] (IGNITE-8657) Simultaneous start of bunch of
client nodes may lead to some clients hangs
[ https://issues.apache.org/jira/browse/IGNITE-8657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16496738#comment-16496738 ]
ASF GitHub Bot commented on IGNITE-8657:
----------------------------------------
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/4102
IGNITE-8657 client reconnect on exchange history exhausted implementation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8657
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4102.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4102
----
commit 4d6cf7331c554dedd5e0f1bb2ef53e2403494cbb
Author: Sergey Chugunov <se...@...>
Date: 2018-05-31T15:34:42Z
IGNITE-8657 client reconnect on exchange history exhausted implementation
----
> 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)