ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8657) Simultaneous start of bunch of client nodes may lead to some clients hangs
Date Wed, 06 Jun 2018 10:40:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-8657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503110#comment-16503110
] 

Alexey Goncharuk commented on IGNITE-8657:
------------------------------------------

Sergey, changes look good to me, but I have some suggestions for the test completeness:

1) Please verify that after the client is connected to the grid, it has the same affinity
mapping as servers (you can match mapPartitionToNodes for the client and a server)
2) Add some cache put/get operations to verify that the client is operational
3) Check that after the last client is connected, all nodes have the same ready affinity topology
version

> 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)

Mime
View raw message