hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3959) [HOD] --resource_manager.options is not passed to qsub
Date Mon, 15 Sep 2008 13:01:45 GMT

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

Vinod K V updated HADOOP-3959:

    Attachment: HADOOP-3959-20080915.txt

Craig, sorry for holding this up this long. I've seen the patch you've attached, it has some
problems. The way you are passing resource_manager.options as nodepooldesc is correct. But
the way you've fixed the error that comes up while enabling resource_manager options is not
correct. It also is making HOD fail after allocation for me, not for you?

In the code, all keyval pairs used anywhere are formed only by string keys and string values,
so assuming an int value and casting it to a string seems to be incorrect. The actual reason
why such an int came in was when you enable resource_manager.options, l:nodes is set by HOD
to an integer value. I changed it to pass it as a string. This seems to be the correct fix,
can you please check this and verify if this works for you? Thanks.

> [HOD] --resource_manager.options is not passed to qsub
> ------------------------------------------------------
>                 Key: HADOOP-3959
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3959
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/hod
>    Affects Versions: 0.17.1
>         Environment: Torque
>            Reporter: Craig Macdonald
>             Fix For: 0.19.0
>         Attachments: HADOOP-3959-20080915.txt, HADOOP-3959.v1.patch
> --resource_manager.options is ignored in HOD. It isnt passed to the qsub command. This
is a problem, as it makes it impossible to add additional resource contraints for scheduling
(i.e. give me 64bit nodes)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message