[
https://issues.apache.org/jira/browse/IGNITE-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901616#comment-14901616
]
ASF GitHub Bot commented on IGNITE-1522:
----------------------------------------
GitHub user vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/103
IGNITE-1522 - Made cache entry listener configurations transient
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator-ignite ignite-1522
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/103.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 #103
----
commit b6de049252411c2c1e13e00803adf5312cf3eb8a
Author: Valentin Kulichenko <[email protected]>
Date: 2015-09-21T23:31:51Z
IGNITE-1522 - Made cache entry listener configurations transient in cache
configuration
----
> Cache entry listener is executed on a joining node
> --------------------------------------------------
>
> Key: IGNITE-1522
> URL: https://issues.apache.org/jira/browse/IGNITE-1522
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Reporter: Valentin Kulichenko
> Assignee: Valentin Kulichenko
> Priority: Blocker
> Fix For: ignite-1.4
>
>
> Scenario is the following:
> # Start first node.
> # Register cache entry listener. Its configuration is added to cache
> configuration (required by JCache).
> # Start second node.
> # As a result entry listener configuration is serialized as a part of cache
> configuration, which is wrong. Moreover, it's executed on this new node.
> Need to make listener configurations transient.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
