[ https://issues.apache.org/jira/browse/YARN-6416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637073#comment-16637073 ]
ASF GitHub Bot commented on YARN-6416: -------------------------------------- GitHub user vbmudalige opened a pull request: https://github.com/apache/hadoop/pull/423 YARN-6416. SIGNAL_CMD argument number is wrong You can merge this pull request into a Git repository by running: $ git pull https://github.com/vbmudalige/hadoop YARN-6416 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/hadoop/pull/423.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #423 ---- commit b2532663babcf4ef4560fb8067b922e61638679e Author: Vidura Mudalige <vidura.mudalige@...> Date: 2018-10-03T15:13:44Z YARN-6416. SIGNAL_CMD argument number is wrong ---- > SIGNAL_CMD argument number is wrong > ----------------------------------- > > Key: YARN-6416 > URL: https://issues.apache.org/jira/browse/YARN-6416 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Miklos Szegedi > Priority: Minor > Labels: newbie > > Yarn application signal command has two arguments, so the number below should > be 2 I think. > {code} > opts.getOption(SIGNAL_CMD).setArgs(3); > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org