You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Seth Call (JIRA)" <ji...@apache.org> on 2018/08/16 21:12:00 UTC
[jira] [Updated] (YARN-8674) MiniClusters do not expose
ResourceManager REST APIs
[ https://issues.apache.org/jira/browse/YARN-8674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Seth Call updated YARN-8674:
----------------------------
Description:
When I use a mini cluster that starts ResourceManager (say MiniYARNCluster), I can not access /ws/v1/cluster/info
It will fail with a 'controller v1 not found'.
However, I did notice something: when the cluster is starting, for just a *split second* it works, and then it permanently goes away.
This leads me to believe that the problem here is that because there are so many YARN components running in the same process, there are multiple Guice injectors (this warning statement does show), and so due to a hard to understanding startup/configuration issue, the @Path of RMWebServices gets overwritten as other components start up.
That's just my guess.
I tried creating a MiniCluster with 0 Resource Managers (with the idea that I'd create a second one with no node managers), but that does not work. Any workarounds would be greatly appreciated!
was:
When I use a mini cluster that starts ResourceManager (say MiniYARNCluster), I can not access /ws/v1/cluster/info?
It will fail with a 'controller v1 not found'.
However, I did notice something: when the cluster is starting, for just a *split second* it works, and then it permanently goes away.
This leads me to believe that the problem here is that because there are so many YARN components running in the same process, there are multiple Guice injectors (this warning statement does show), and so due to a hard to understanding startup/configuration issue, the @Path of RMWebServices gets overwritten as other components start up.
That's just my guess.
I tried creating a MiniCluster with 0 Resource Managers (with the idea that I'd create a second one with no node managers), but that does not work. Any workarounds would be greatly appreciated!
> MiniClusters do not expose ResourceManager REST APIs
> ----------------------------------------------------
>
> Key: YARN-8674
> URL: https://issues.apache.org/jira/browse/YARN-8674
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.6.5, 2.8.2
> Reporter: Seth Call
> Priority: Major
>
> When I use a mini cluster that starts ResourceManager (say MiniYARNCluster), I can not access /ws/v1/cluster/info
>
> It will fail with a 'controller v1 not found'.
>
> However, I did notice something: when the cluster is starting, for just a *split second* it works, and then it permanently goes away.
>
> This leads me to believe that the problem here is that because there are so many YARN components running in the same process, there are multiple Guice injectors (this warning statement does show), and so due to a hard to understanding startup/configuration issue, the @Path of RMWebServices gets overwritten as other components start up.
> That's just my guess.
>
> I tried creating a MiniCluster with 0 Resource Managers (with the idea that I'd create a second one with no node managers), but that does not work. Any workarounds would be greatly appreciated!
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org