[
https://issues.apache.org/jira/browse/YARN-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729465#comment-17729465
]
Jon Bringhurst edited comment on YARN-7747 at 6/5/23 8:36 PM:
--------------------------------------------------------------
I think I just ran into this issue on 3.3.5. After launching a MiniCluster RM
and NM, the URL to the RM shows the NM UI.
I'm going to try to patch locally with the patch here (it mostly still applies)
to see if it resolves things.
was (Author: jonbringhurst):
I think I just ran into this issue on 3.3.5. After launching a MiniCluster RM
and NM, the URL to the RM shows the NM UI.
> YARN UI is broken in the minicluster
> -------------------------------------
>
> Key: YARN-7747
> URL: https://issues.apache.org/jira/browse/YARN-7747
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Gera Shegalov
> Assignee: Gera Shegalov
> Priority: Major
> Attachments: YARN-7747.001.patch, YARN-7747.002.patch
>
>
> YARN web apps use non-injected instances of GuiceFilter, i.e. instances
> created by Jetty as opposed by Guice itself. This triggers the [call
> path|https://github.com/google/guice/blob/master/extensions/servlet/src/com/google/inject/servlet/GuiceFilter.java#L251]
> where the static field {{pipeline}} is used instead of the instance field
> {{injectedPipeline}}. However, besides GuiceFilter instances created by
> Jetty, each Guice module generates them as well. On the injection call path
> this static variable is updated by each instance. Thus if there are multiple
> modules as it happens to be the case in the minicluster the one loaded last
> ends up defining the filter pipeline for all Jetty instances. In the
> minicluster case this is the nodemanager UI
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
