You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Shilun Fan (Jira)" <ji...@apache.org> on 2026/03/02 22:34:00 UTC

[jira] [Resolved] (YARN-11897) NodeManager REST API backward compatibility with Jersey1

     [ https://issues.apache.org/jira/browse/YARN-11897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shilun Fan resolved YARN-11897.
-------------------------------
    Fix Version/s: 3.5.0
                   3.5.1
     Hadoop Flags: Reviewed
       Resolution: Fixed

> 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
>             Fix For: 3.5.0, 3.5.1
>
>
> 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: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org