You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Josh Wills (JIRA)" <ji...@apache.org> on 2015/01/23 08:13:35 UTC

[jira] [Updated] (CRUNCH-490) Prefer mapreduce.framework.name for determining which version of MR is running

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

Josh Wills updated CRUNCH-490:
------------------------------
    Attachment: CRUNCH-490.patch

Tiny patch for this, was planning on committing it tomorrow.

> Prefer mapreduce.framework.name for determining which version of MR is running
> ------------------------------------------------------------------------------
>
>                 Key: CRUNCH-490
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-490
>             Project: Crunch
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.11.0
>            Reporter: Josh Wills
>            Assignee: Josh Wills
>            Priority: Minor
>             Fix For: 0.12.0
>
>         Attachments: CRUNCH-490.patch
>
>
> We use a different poll interval for the MRExecutor depending on whether or not we're running in local mode, and we determine whether or not we're running in local mode based on the value of the mapreduce.jobtracker.address property in the configuration. However, a more reliable way to do this is by checking the mapreduce.framework.name, esp. for yarn-based jobs that will not have a meaningful value for the jobtracker property.



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