[
https://issues.apache.org/jira/browse/YARN-9573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853168#comment-16853168
]
Adam Antal commented on YARN-9573:
----------------------------------
I couldn't get any further with this patch, because I couldn't start the
TestDistributedShell tests locally. The logs are always filled up with the
following stacktraces: (outputting like 800MB log during the 90sec timeout
period):
{noformat}
2019-05-31 17:54:08,972 WARN [IPC Server Responder] ipc.Server
(Server.java:doRunLoop(1546)) - Exception in Responder
java.io.IOException: Invalid argument
at sun.nio.ch.KQueueArrayWrapper.kevent0(Native Method)
at sun.nio.ch.KQueueArrayWrapper.poll(KQueueArrayWrapper.java:198)
at sun.nio.ch.KQueueSelectorImpl.doSelect(KQueueSelectorImpl.java:117)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
at org.apache.hadoop.ipc.Server$Responder.doRunLoop(Server.java:1485)
at org.apache.hadoop.ipc.Server$Responder.run(Server.java:1468)
{noformat}
This is probably some local issue at my computer. Anyone has seen something
similar to this before?
> DistributedShell cannot specify LogAggregationContext
> -----------------------------------------------------
>
> Key: YARN-9573
> URL: https://issues.apache.org/jira/browse/YARN-9573
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: distributed-shell, log-aggregation, yarn
> Affects Versions: 3.2.0
> Reporter: Adam Antal
> Assignee: Adam Antal
> Priority: Major
> Attachments: YARN-9573.001.patch
>
>
> When DShell sends the application request object to the RM, it doesn't
> specify the LogAggregationContext object - thus it is not possible to run
> DShell with various log-aggregation configurations, for e.g. a rolling
> fashioned log aggregation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]