HOD Should Be Less Restrictive Over Options Passed To Resource Manager
----------------------------------------------------------------------
Key: HADOOP-8081
URL: https://issues.apache.org/jira/browse/HADOOP-8081
Project: Hadoop Common
Issue Type: Wish
Components: contrib/hod
Affects Versions: 1.0.0, 0.21.0
Reporter: Ben Smithers
Priority: Minor
At present, HOD requires any extra options passed to the resource manager to be
of the form <option>:<sub-option>=<value>
This is quite restrictive. Considering Torque and qsub, this effectively limits
the options to a subset of the resource constraints, variable lists and
additional attributes. Potentially desirable attributes that cannot (to the
best of my knowledge) be expressed:
- Mailing options. Given than it may take some time for a long-running HOD job
to be scheduled, it would be useful to exploit the options (-m and -M) for
notifying users
- Other resource constraints, such as particular nodes or number of processors
per node. The format required by
qsub(http://www.clusterresources.com/torquedocs/2.1jobsubmission.shtml#nodeExamples)
is incompatible with the format required by HOD. In practice, it would
probably be desirable to have these options specified via the command line as
these may change per HOD job
I imagine some thought would be needed to balance flexibility whist not
breaking the options HOD sets by default.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
