[
https://issues.apache.org/jira/browse/IGNITE-8657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512350#comment-16512350
]
Sergey Chugunov edited comment on IGNITE-8657 at 6/14/18 11:38 AM:
-------------------------------------------------------------------
I've covered last corner case with forceServerMode clients and refactored code
a little bit.
Latest TC run looks acceptable, most of suites with execution timeout or other
unlucky results were restarted, these results are not reproducible.
[latest
RunAll|https://ci.ignite.apache.org/viewLog.html?buildId=1386252&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll]
Specifically BinaryObject Simple Mapper Basic has passed: [latest
run|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_BinaryObjectsSimpleMapperBasic].
was (Author: sergey-chugunov):
I've covered last corner case with forceServerMode clients and refactored code
a little bit.
Latest TC run looks acceptable, most of suites with execution timeout or other
unlucky results were restarted, these results are not reproducible.
https://ci.ignite.apache.org/viewLog.html?buildId=1386252&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll
> 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)
