You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2016/09/27 13:22:20 UTC

[jira] [Resolved] (IGNITE-3967) Discovery events can be lost after client reconnect

     [ https://issues.apache.org/jira/browse/IGNITE-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Semen Boikov resolved IGNITE-3967.
----------------------------------
    Resolution: Fixed
      Assignee:     (was: Semen Boikov)

Fixed to to use single removes to clear map.

> Discovery events can be lost after client reconnect
> ---------------------------------------------------
>
>                 Key: IGNITE-3967
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3967
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 1.5.0.final
>            Reporter: Semen Boikov
>            Priority: Critical
>             Fix For: 1.8
>
>
> GridDiscoveryManager uses GridBoundedConcurrentOrderedMap to store discovery events history. When client reconnects this collection is cleared using 'clear' method, but for GridBoundedConcurrentOrderedMap this method is not correctly implemented, and after this elements put in this map can be lost.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)