[
https://issues.apache.org/jira/browse/YARN-11891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18035641#comment-18035641
]
ASF GitHub Bot commented on YARN-11891:
---------------------------------------
dmmkr opened a new pull request, #8057:
URL: https://github.com/apache/hadoop/pull/8057
### Description of PR
filter() method inside the ClientJerseyRetryFilter class, calls
checkUrlConnectivity() in a while loop, If there is any issue with
connectivity, it decrements the leftRetries till it becomes 0 and throws an
Exception, but if it succeeds it keeps on spinning inside the infinite while
loop, so added a return after checkUrlConnectivity().
After fixing the above issue, the yarn logs command was throwing below error.
Can not find any log file matching the pattern: [ALL] for the container:
container_id within the application: app_id
The XML response of /ws/v1/node/containers/<container_id>/logs is
`<containerLogsInfoes>
<containerLogsInfo>
<containerLogInfo>
<fileName>stdout</fileName>
<fileSize>0</fileSize>
<lastModifiedTime>Wed Nov 05 19:41:59 +0530 2025</lastModifiedTime>
</containerLogInfo>
<containerLogInfo>
<fileName>prelaunch.out</fileName>
<fileSize>100</fileSize>
<lastModifiedTime>Wed Nov 05 19:41:59 +0530 2025</lastModifiedTime>
</containerLogInfo>
<containerLogInfo>
<fileName>launch_container.sh</fileName>
<fileSize>6125</fileSize>
<lastModifiedTime>Wed Nov 05 19:41:59 +0530 2025</lastModifiedTime>
</containerLogInfo>
<containerLogInfo>
<fileName>directory.info</fileName>
<fileSize>2336</fileSize>
<lastModifiedTime>Wed Nov 05 19:41:59 +0530 2025</lastModifiedTime>
</containerLogInfo>
<containerLogInfo>
<fileName>prelaunch.err</fileName>
<fileSize>0</fileSize>
<lastModifiedTime>Wed Nov 05 19:41:59 +0530 2025</lastModifiedTime>
</containerLogInfo>
<containerLogInfo>
<fileName>syslog</fileName>
<fileSize>77682</fileSize>
<lastModifiedTime>Wed Nov 05 19:42:21 +0530 2025</lastModifiedTime>
</containerLogInfo>
<containerLogInfo>
<fileName>stderr</fileName>
<fileSize>0</fileSize>
<lastModifiedTime>Wed Nov 05 19:41:59 +0530 2025</lastModifiedTime>
</containerLogInfo>
<logAggregationType>LOCAL</logAggregationType>
<containerId>container_id</containerId>
<nodeId>hostname:42923</nodeId>
</containerLogsInfo>
</containerLogsInfoes>`
So in getContainerLogFiles(), an additional
getJSONObject("containerLogsInfoes") has been added to ensure the XML response
is parsed properly
### How was this patch tested?
Validated yarn logs -applicationId <appID> for running and completed
applications.
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> Yarn logs command hangs for running applications
> ------------------------------------------------
>
> Key: YARN-11891
> URL: https://issues.apache.org/jira/browse/YARN-11891
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 3.5.0
> Reporter: D M Murali Krishna Reddy
> Assignee: D M Murali Krishna Reddy
> Priority: Major
>
> After the jersey upgrade HADOOP-15984
> Yarn logs command for a running application, hangs printing the below log.
> {code:java}
> bin/yarn logs -applicationId application_1762350876472_0002
> 2025-11-05 19:28:30,353 INFO client.DefaultNoHARMFailoverProxyProvider:
> Connecting to ResourceManager at /0.0.0.0:8032
> 2025-11-05 19:28:31,019 INFO util.log: Logging initialized @1630ms to
> org.eclipse.jetty.util.log.Slf4jLog
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
