[
https://issues.apache.org/jira/browse/YARN-10161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046993#comment-17046993
]
Hudson commented on YARN-10161:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #18009 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/18009/])
YARN-10161. TestRouterWebServicesREST is corrupting STDOUT. Contributed
(inigoiri: rev a43510e21d01e6c78e98e7ad9469cbea70a66466)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-router/src/test/java/org/apache/hadoop/yarn/server/router/webapp/JavaProcess.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-router/src/test/java/org/apache/hadoop/yarn/server/router/webapp/TestRouterWebServicesREST.java
> TestRouterWebServicesREST is corrupting STDOUT
> ----------------------------------------------
>
> Key: YARN-10161
> URL: https://issues.apache.org/jira/browse/YARN-10161
> Project: Hadoop YARN
> Issue Type: Test
> Components: yarn
> Affects Versions: 2.10.0, 3.2.1
> Reporter: Jim Brennan
> Assignee: Jim Brennan
> Priority: Minor
> Attachments: YARN-10161.001.patch, YARN-10161.002.patch,
> YARN-10161.003.patch
>
>
> TestRouterWebServicesREST is creating processes that inherit stdin/stdout
> from the current process, so the output from those jobs goes into the
> standard output of mvn test.
> Here's an example from a recent build:
> {noformat}
> [WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM
> 1. See FAQ web page and the dump file
> /testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-router/target/surefire-reports/2020-02-24T08-00-54_776-jvmRun1.dumpstream
> [INFO] Tests run: 41, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> 41.644 s - in
> org.apache.hadoop.yarn.server.router.webapp.TestRouterWebServicesREST
> [WARNING] ForkStarter IOException: 506 INFO [main]
> resourcemanager.ResourceManager (LogAdapter.java:info(49)) - STARTUP_MSG:
> 522 INFO [main] resourcemanager.ResourceManager (LogAdapter.java:info(49)) -
> registered UNIX signal handlers for [TERM, HUP, INT]
> 876 INFO [main] conf.Configuration
> (Configuration.java:getConfResourceAsInputStream(2588)) - core-site.xml not
> found
> 879 INFO [main] security.Groups (Groups.java:refresh(402)) - clearing
> userToGroupsMap cache
> 930 INFO [main] conf.Configuration
> (Configuration.java:getConfResourceAsInputStream(2588)) - resource-types.xml
> not found
> 930 INFO [main] resource.ResourceUtils
> (ResourceUtils.java:addResourcesFileToConf(421)) - Unable to find
> 'resource-types.xml'.
> 940 INFO [main] resource.ResourceUtils
> (ResourceUtils.java:addMandatoryResources(126)) - Adding resource type - name
> = memory-mb, units = Mi, type = COUNTABLE
> 940 INFO [main] resource.ResourceUtils
> (ResourceUtils.java:addMandatoryResources(135)) - Adding resource type - name
> = vcores, units = , type = COUNTABLE
> 974 INFO [main] conf.Configuration
> (Configuration.java:getConfResourceAsInputStream(2591)) - found resource
> yarn-site.xml at
> file:/testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-router/target/test-classes/yarn-site.xml
> 001 INFO [main] event.AsyncDispatcher (AsyncDispatcher.java:register(227)) -
> Registering class
> org.apache.hadoop.yarn.server.resourcemanager.RMFatalEventType for class
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$RMFatalEventDispatcher
> 053 INFO [main] security.NMTokenSecretManagerInRM
> (NMTokenSecretManagerInRM.java:<init>(75)) - NMTokenKeyRollingInterval:
> 86400000ms and NMTokenKeyActivationDelay: 900000ms
> 060 INFO [main] security.RMContainerTokenSecretManager
> (RMContainerTokenSecretManager.java:<init>(79)) -
> ContainerTokenKeyRollingInterval: 86400000ms and
> ContainerTokenKeyActivationDelay: 900000ms
> ... {noformat}
> It seems like these processes should be rerouting stdout/stderr to a file
> instead of dumping it to the console.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
