[
https://issues.apache.org/jira/browse/IGNITE-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324103#comment-15324103
]
Denis Magda commented on IGNITE-3151:
-------------------------------------
[~v.pyatkov] Please see my review notes in the pull-request.
Aslo I would add the same test but when a half of the nodes are client nodes.
Client nodes receive update notifications a bit later and we must be sure that
your fix didn't break anything.
> Using IgniteCountDownLatch sometimes drives to dead lock.
> ---------------------------------------------------------
>
> Key: IGNITE-3151
> URL: https://issues.apache.org/jira/browse/IGNITE-3151
> Project: Ignite
> Issue Type: Bug
> Reporter: Vladislav Pyatkov
> Assignee: Vladislav Pyatkov
> Attachments: igniteBugShot.zip
>
>
> Run several serve node (recoment use count of CPU - 1).
> Wait update topology.
> Run client
> After some iteration exception will thrown (In my case it take place after
> around 10K iteration).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
