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-3167) Hadoop: restore external execution.
Date Mon, 10 Jul 2017 07:08:05 GMT

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

Vladimir Ozerov updated IGNITE-3167:
------------------------------------
    Fix Version/s:     (was: 2.1)
                   2.2

> Hadoop: restore external execution.
> -----------------------------------
>
>                 Key: IGNITE-3167
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3167
>             Project: Ignite
>          Issue Type: Task
>          Components: hadoop
>    Affects Versions: 1.5.0.final
>            Reporter: Vladimir Ozerov
>            Priority: Critical
>             Fix For: 2.2
>
>
> Some time ago we decided to get rid external execution mode. It appears to be a wrong
decision.
> Hadoop users rely on its process-per-job nature in lot's places. One of such case could
be observed in HiBench Bayes benchmark:
> 1) Job creates something in the local file system through Hadoop FileSystem API.
> 2) Then it tries to get this data using regular java.io.FileReader and relative paths.

> This doesn't work in embedded mode because our LocalFileSystem wrapper assigns different
work dirs for jobs, but process-wide working directory is always the same. As a result, aforementioned
benchmark doesn't work in Ignite, but work with standard Hadoop job tracker.
> It seems that we must return external execution back.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message