ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yakov Zhdanov <yzhda...@apache.org>
Subject P2P Deployment - Local Ownership Flag
Date Wed, 30 Aug 2017 13:36:37 GMT
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



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message