You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ershov (JIRA)" <ji...@apache.org> on 2015/12/23 10:04:46 UTC

[jira] [Commented] (IGNITE-2032) Filters passed to ScanQuery are not redeployed when originating from a client node

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

Vladimir Ershov commented on IGNITE-2032:
-----------------------------------------

As found: during GridDeploymentPerVersionStore#onEvent clsLoader that should be cleaned from IgniteUtils.classCache is GridDeploymentClassLoader, but actual classes registered under CacheClassLoader. I'm going to discuss possible modification for that mechanism since it looks broken. As for server mode, it is working cos for server node we do unwind->onDeploy before deployment which is also strange.

> Filters passed to ScanQuery are not redeployed when originating from a client node
> ----------------------------------------------------------------------------------
>
>                 Key: IGNITE-2032
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2032
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: ignite-1.4
>            Reporter: Denis Magda
>            Assignee: Vladimir Ershov
>            Priority: Critical
>             Fix For: 1.6
>
>         Attachments: ScanQueryFailure.java, test-config.xml
>
>
> The following case doesn't work:
> - start a standalone server node with peer class loading enabled;
> - start a client node, populate a cache with data, perform a scan query using a filter;
> - since the server doesn't have the filter in its classpath it will load it from the client. Everything works fine here;
> - stop the client, the server will undeploy the filter. No issue here so far;
> - modify the filter a bit and start the client one more time. The server won't deploy the new version of the filter and will be using the old regardless of the fact that it was undeployed before according to the logs.
> The server can be started using ignite.bat and test-config.xml (attached).
> The source of the client is located in attached ScanQueryFailure.java.
> BTW, everything works fine if to use the server mode instead of the client one.



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