[
https://issues.apache.org/jira/browse/SLIDER-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran reopened SLIDER-562:
-----------------------------------
causing mock yarn tests such as {{TestMockAppStateContainerFailure}} to fail:
{code}
org.apache.slider.core.exceptions.BadConfigException: Missing option
yarn.role.priority
at
org.apache.slider.core.conf.MapOperations.getMandatoryOption(MapOperations.java:115)
at
org.apache.slider.server.appmaster.state.AppState.createDynamicProviderRole(AppState.java:583)
at
org.apache.slider.server.appmaster.state.AppState.buildInstance(AppState.java:508)
at
org.apache.slider.server.appmaster.model.mock.BaseMockAppStateTest.initApp(BaseMockAppStateTest.groovy:100)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
{code}
> Statistics for slider-appmaster on AM UI are inaccurate
> -------------------------------------------------------
>
> Key: SLIDER-562
> URL: https://issues.apache.org/jira/browse/SLIDER-562
> Project: Slider
> Issue Type: Bug
> Components: appmaster, Web & REST
> Reporter: Jonathan Maron
> Assignee: Steve Loughran
> Fix For: Slider 0.60
>
> Attachments: Screen Shot 2014-10-28 at 14.05.32.png,
> Screenshot_10_23_14__11_21_AM.jpeg
>
>
> The statistics displayed for the slider-appmaster are inaccurate - the number
> of "actual" displayed is '0', even though you're viewing a page presented by
> the running appmaster ;)
> I would imagine there's a need to increment the RoleStatus of the
> slider-appmaster component at the appropriate time(s) (as opposed to the
> other components getting updated by the app master itself)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
