[
https://issues.apache.org/jira/browse/SLIDER-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086706#comment-14086706
]
Steve Loughran commented on SLIDER-270:
---------------------------------------
It's in slider
{code}
- AMRMClientAsync.onError() received java.lang.AssertionError: Container still
in active container list
java.lang.AssertionError: Container still in active container list
at
org.apache.slider.server.appmaster.state.AppState.onCompletedNode(AppState.java:1271)
at
org.apache.slider.server.appmaster.SliderAppMaster.onContainersCompleted(SliderAppMaster.java:1059)
at
org.apache.hadoop.yarn.client.api.async.impl.AMRMClientAsyncImpl$CallbackHandlerThread.run(AMRMClientAsyncImpl.java:303)
2014-08-05 21:32:59,042 [AMRM Callback Handler Thread] ERROR
yarn.YarnUncaughtExceptionHandler
(YarnUncaughtExceptionHandler.java:uncaughtException(68)) - Thread Thread[AMRM
Callback Handler Thread,5,main] threw an Exception.
org.apache.hadoop.yarn.exceptions.YarnRuntimeException:
java.lang.AssertionError: Container still in active container list
at
org.apache.hadoop.yarn.client.api.async.impl.AMRMClientAsyncImpl$CallbackHandlerThread.run(AMRMClientAsyncImpl.java:315)
Caused by: java.lang.AssertionError: Container still in active container list
at
org.apache.slider.server.appmaster.state.AppState.onCompletedNode(AppState.java:1271)
at
org.apache.slider.server.appmaster.SliderAppMaster.onContainersCompleted(SliderAppMaster.java:1059)
at
org.apache.hadoop.yarn.client.api.async.impl.AMRMClientAsyncImpl$CallbackHandlerThread.run(AMRMClientAsyncImpl.java:303)
{code}
> Calling flex (down) the second time does not work
> -------------------------------------------------
>
> Key: SLIDER-270
> URL: https://issues.apache.org/jira/browse/SLIDER-270
> Project: Slider
> Issue Type: Bug
> Components: appmaster
> Affects Versions: Slider 0.50
> Reporter: Sumit Mohanty
> Assignee: Steve Loughran
> Fix For: Slider 0.50
>
>
> From AppMaster log (see below) it looks like that the second command to flex
> from 2 to 1 did not result in container release.
> {noformat}
> 14/08/04 01:55:18 INFO state.AppState: Role MEMCACHED flexed from 3 to 2
> 14/08/04 01:55:18 INFO state.AppState: RoleStatus{name='MEMCACHED', key=1,
> desired=2, actual=3, requested=0, releasing=0, failed=0, started=3,
> startFailed=0, completed=0, failureMessage=''}
> 14/08/04 01:55:18 INFO state.AppState: MEMCACHED: Asking for 1 fewer node(s)
> for a total of 2
> 14/08/04 01:55:19 INFO appmaster.SliderAppMaster: onContainersCompleted([1]
> 14/08/04 01:55:19 INFO appmaster.SliderAppMaster: Container Completion for
> containerID=container_1405048900371_0054_01_000004, state=COMPLETE,
> exitStatus=-100, diagnostics=Container released by application
> 14/08/04 01:55:19 INFO state.AppState: Container was queued for release
> 14/08/04 01:55:19 INFO state.AppState: decrementing role count for role
> MEMCACHED
> 14/08/04 01:55:19 INFO agent.AgentProviderService: Removing container
> specific data for container_1405048900371_0054_01_000004
> 14/08/04 01:55:19 INFO agent.AgentProviderService: publishing
> PublishedConfiguration{description='ComponentInstanceData' entries = 2}
> 14/08/04 01:55:19 INFO state.AppState: RoleStatus{name='MEMCACHED', key=1,
> desired=2, actual=2, requested=0, releasing=0, failed=0, started=3,
> startFailed=0, completed=1, failureMessage=''}
> 14/08/04 01:55:45 INFO state.AppState: Role MEMCACHED flexed from 2 to 1
> 14/08/04 01:55:45 INFO state.AppState: RoleStatus{name='MEMCACHED', key=1,
> desired=1, actual=2, requested=0, releasing=0, failed=0, started=3,
> startFailed=0, completed=1, failureMessage=''}
> 14/08/04 01:55:45 INFO state.AppState: MEMCACHED: Asking for 1 fewer node(s)
> for a total of 1
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
