You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Mikhail Cherkasov (JIRA)" <ji...@apache.org> on 2018/09/10 23:01:00 UTC

[jira] [Resolved] (IGNITE-9527) NPE in CacheLateAffinityAssignmentTest#testNoForceKeysRequests test

     [ https://issues.apache.org/jira/browse/IGNITE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mikhail Cherkasov resolved IGNITE-9527.
---------------------------------------
    Resolution: Not A Problem

5510 fixed the issue completely, can't reproduce on master.

> NPE in CacheLateAffinityAssignmentTest#testNoForceKeysRequests test
> -------------------------------------------------------------------
>
>                 Key: IGNITE-9527
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9527
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Mikhail Cherkasov
>            Assignee: Mikhail Cherkasov
>            Priority: Major
>
> The wrong assertion was removed by the following ticket: https://issues.apache.org/jira/browse/IGNITE-5510, however, NPE exception can be observed in logs, so if [~sboikov] said that this method can be called concurrently and it's valid to have null here, then I think we should remove NPE from logs.



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