[
https://issues.apache.org/jira/browse/IGNITE-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897432#comment-15897432
]
ASF GitHub Bot commented on IGNITE-4779:
----------------------------------------
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/1597
IGNITE-4779 Missed discovery data snapshot during exchange processing
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4779
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1597.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 #1597
----
commit e3ac2d4d7aedd54605eb1932fddd111d91d298c2
Author: Igor Seliverstov <[email protected]>
Date: 2017-03-06T14:51:36Z
[IGNITE-4779] Missed discovery data snapshot during exchange processing
----
> Missed discovery data snapshot during exchange processing
> ---------------------------------------------------------
>
> Key: IGNITE-4779
> URL: https://issues.apache.org/jira/browse/IGNITE-4779
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Reporter: Semen Boikov
> Assignee: Igor Seliverstov
> Priority: Critical
> Fix For: 2.0
>
>
> Currently GridDiscoveryManager stores only 500 last discovery data snapshots,
> if in 'resolveDiscoCache' requested version is not available it just throws
> IgniteException. It is possible while exchange is processed on topology
> version N, lot of discovery events is generated (e.g. in case of client
> caches start) and version N is removed from history. For exchange solution is
> simple: when exchange is triggered need save discovery snapshot in exchange
> future.
> Also need review others places where discovery history is used.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
