You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/03/25 13:49:25 UTC

[jira] [Updated] (IGNITE-2101) NPE when trying to submit Hadoop job to a node where Hadoop module is not loaded.

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

Vladimir Ozerov updated IGNITE-2101:
------------------------------------
    Fix Version/s:     (was: 1.6)
                   1.7

> NPE when trying to submit Hadoop job to a node where Hadoop module is not loaded.
> ---------------------------------------------------------------------------------
>
>                 Key: IGNITE-2101
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2101
>             Project: Ignite
>          Issue Type: Bug
>          Components: hadoop
>    Affects Versions: ignite-1.4
>            Reporter: Vladimir Ozerov
>            Assignee: Ivan Veselovsky
>            Priority: Critical
>             Fix For: 1.7
>
>
> See http://apache-ignite-users.70518.x6.nabble.com/NPE-issue-with-trying-to-submit-Hadoop-MapReduce-td2146.html
> When Hadoop module is not loaded, HadoopNoopProcessor is started on the node. And it's method nextJobId() returns null. This null is then propagated to the client and NPE is raised. There is no way for users to underastand what is wrong.
> Solution should be fairly simple: just throw an exception with sensible message from HadoopNoopProcessor.nextJobId() method. It should be propagated smoothly to the client. 
> Also we need to add tests for this scenario.



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