[jira] [Commented] (MAPREDUCE-5460) MR AppMaster command options does not replace @taskid@ with the current task ID.

["Chris Nauroth (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740295#comment-13740295 ] 

Chris Nauroth commented on MAPREDUCE-5460:
------------------------------------------

Here is what I tested in my {{mapred-site.xml}}:

{code}
  <property>
    <name>yarn.app.mapreduce.am.command-opts</name>
    <value>-Xmx1024m -verbose:gc -Xloggc:/tmp/mr-am-@taskid@.gc</value>
  </property>
{code}

The resulting GC log file was /tmp/mr-am-@taskid@.gc with no substitution.

This feature does work correctly inside the {{mapred.child.java.opts}} property for map and reduce task processes.  I only see the problem with {{yarn.app.mapreduce.am.command-opts}}.

Either there is a bug, which would require a code fix, or the feature isn't really supported for the AM, which would require a documentation fix.  I would prefer that we do support replacement using the unique application ID, because it would be handy to separate GC logs and other things for the AM just like we do for the map and reduce tasks.

                
> MR AppMaster command options does not replace @taskid@ with the current task ID.
> --------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5460
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5460
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: applicationmaster, mrv2
>    Affects Versions: 3.0.0, 2.1.1-beta
>            Reporter: Chris Nauroth
>
> The description of {{yarn.app.mapreduce.am.command-opts}} in mapred-default.xml states that occurrences of {{@taskid@}} will be replaced by the current task ID.  This substitution is not happening.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira