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

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

GitHub user VladimirErshov opened a pull request:

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

    IGNITE-2539 test and commented a way to reproduce

    

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

    $ git pull https://github.com/VladimirErshov/ignite ignite-2539

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

    https://github.com/apache/ignite/pull/451.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 #451
    
----
commit f74793e2c83090ddd0fd0442f1e02addc184450e
Author: vershov <[email protected]>
Date:   2016-02-03T18:00:47Z

    IGNITE-2539 test and commented a way to reproduce

----


> NPE at RendezvousAffinityFunction
> ---------------------------------
>
>                 Key: IGNITE-2539
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2539
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 1.5.0.final
>            Reporter: Vladimir Ershov
>            Assignee: Vladimir Ershov
>            Priority: Critical
>         Attachments: ignite.log
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> RendezvousAffinityFunction#assignPartition throws NPE, probably due to 
> simultaneous topology change and  cache stop. We should write a test and fix 
> this.



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

Reply via email to