ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-2101) NPE when trying to submit Hadoop job to a node where Hadoop module is not loaded.
Date Mon, 11 Jan 2016 15:04:39 GMT

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

Vladimir Ozerov updated IGNITE-2101:
------------------------------------
    Priority: Critical  (was: Blocker)

> 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
>            Priority: Critical
>             Fix For: 1.6
>
>
> 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)

Mime
View raw message