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

ASF GitHub Bot commented on IGNITE-9129:
----------------------------------------

GitHub user Jokser opened a pull request:

    https://github.com/apache/ignite/pull/4457

    IGNITE-9129 Request for user-classes with enabled P2P only after local node 
join

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-9129

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/4457.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 #4457
    
----
commit 60f3e7fd019b3c5d7c86f0cfc57f89eaf15a78e4
Author: Pavel Kovalenko <jokserfn@...>
Date:   2018-07-30T16:37:13Z

    IGNITE-9129 Request for user-classes with enabled P2P asynchronously after 
local node join

----


> P2P class deployment is failed when using ZK discovery
> ------------------------------------------------------
>
>                 Key: IGNITE-9129
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9129
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.5, 2.6
>            Reporter: Pavel Kovalenko
>            Assignee: Pavel Kovalenko
>            Priority: Critical
>             Fix For: 2.7
>
>
> In case of using Zookeeper Discovery, cluster node which joins to a cluster 
> receives information that some user-classes have been already deployed but 
> doesn't exist in the local classpath. In this case, the node tries to request 
> for these classes from nodes that contain it, but do it synchronously during 
> Zookeeper Discovery starting and gets NullPointer when first topology 
> snapshot has not initialized yet.
> We should request for user-classes asynchronously and only after the first 
> topology has initialized.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to