P2P Deployment - Local Ownership Flag

[Yakov Zhdanov <yz...@apache.org>]

Igniters, esp. Alex Goncharuk,

There was a problem recently discovered
with org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager#locDepOwner

As far as I remember, this flag is automatically set if Ignite detects
public API usage outside of deployment class loader that implies this is
user code execution and therefore this node most probably owns classes that
may be requested from server nodes.

[PROBLEM] It seems when this flag was introduced, we have missed a use case
when server nodes may have some user classes on board which use Ignite's
public API and therefore local deployment ownership is set to true for
them. Topology also contains clients that have broader classpath, but
servers may send requests to other servers that have mistakenly set the
flag to true.

As a temporary solution I would suggest to consider
https://issues.apache.org/jira/browse/IGNITE-6213.

Thoughts?

--Yakov

Re: P2P Deployment - Local Ownership Flag

[Dmitry Pavlov <dp...@gmail.com>]

Hi Igniters,



I assume this may be related to case desctibed by user in
http://apache-ignite-users.70518.x6.nabble.com/Understanding-the-mechanics-of-peer-class-loading-td12661.html



We didn't managed to create a reproducer for this issue.

But case is similar:

- server has cache classes in it's classpath.

- And servers sends requests (messages) to other servers.

P2P deployment problem occurred sometimes during message sending.



Sincerely,

Dmitriy Pavlov


ср, 30 авг. 2017 г. в 16:36, Yakov Zhdanov <yz...@apache.org>:

> Igniters, esp. Alex Goncharuk,
>
> There was a problem recently discovered
> with
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager#locDepOwner
>
> As far as I remember, this flag is automatically set if Ignite detects
> public API usage outside of deployment class loader that implies this is
> user code execution and therefore this node most probably owns classes that
> may be requested from server nodes.
>
> [PROBLEM] It seems when this flag was introduced, we have missed a use case
> when server nodes may have some user classes on board which use Ignite's
> public API and therefore local deployment ownership is set to true for
> them. Topology also contains clients that have broader classpath, but
> servers may send requests to other servers that have mistakenly set the
> flag to true.
>
> As a temporary solution I would suggest to consider
> https://issues.apache.org/jira/browse/IGNITE-6213.
>
> Thoughts?
>
> --Yakov
>