[
https://issues.apache.org/jira/browse/YARN-11897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18058072#comment-18058072
]
ASF GitHub Bot commented on YARN-11897:
---------------------------------------
Hean-Chhinling commented on PR #8227:
URL: https://github.com/apache/hadoop/pull/8227#issuecomment-3889501608
Why the Hadoop Yetus has not commented at all?
Seems to be a problem it could not detect that there is a new commit in the
trunk_YARN-11897 branch.
Will try to push one more time and see.
```
17:33:31 Already up to date.
17:33:31 Already on 'trunk'
17:33:31 Your branch is up to date with 'origin/trunk'.
17:33:31 HEAD is now at fd18f0647dc HADOOP-19808. Jenkins switch from
Debian 11 to Debian 13
17:33:32 ERROR: https://github.com/apache/hadoop/pull/8227 does not apply
to trunk.
```
> NodeManager REST API backward compatibility with Jersey1
> --------------------------------------------------------
>
> Key: YARN-11897
> URL: https://issues.apache.org/jira/browse/YARN-11897
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: yarn
> Affects Versions: 3.5.0
> Reporter: Peter Szucs
> Assignee: chhinlinghean
> Priority: Major
> Labels: pull-request-available
>
> Jersey 2 upgrade broke NM REST API, so nodes applications page is not
> rendering in yarn UI v2 and also logs CLI cannot retrieve container logs.
> To fix this we need to:
> * introduce moxy in NM similar to YARN-11874
> * "/containers/\{containerid}/logs" endpoint returns a list, which will
> always be generated as a JSON array with Jersey 2. In Jersey 1 it returned a
> JSON object in case the list had a single element, and logs CLI expects a
> JSON object as well when calling this endpoint. That should be changed to
> keep backward compatibility. With returning a wrapper object instead of a
> list we could achieve the same behaviour.
> * Fix unit tests
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
