You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "kyungwan nam (JIRA)" <ji...@apache.org> on 2016/08/05 08:31:20 UTC
[jira] [Updated] (SLIDER-1163) app_container_tag is greater than
the number of component instances
[ https://issues.apache.org/jira/browse/SLIDER-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
kyungwan nam updated SLIDER-1163:
---------------------------------
Attachment: SLIDER-1163_develop.patch
I attached a patch.
> app_container_tag is greater than the number of component instances
> -------------------------------------------------------------------
>
> Key: SLIDER-1163
> URL: https://issues.apache.org/jira/browse/SLIDER-1163
> Project: Slider
> Issue Type: Bug
> Affects Versions: Slider 0.81
> Reporter: kyungwan nam
> Attachments: SLIDER-1163_develop.patch
>
>
> the way to reproduce this issue
> - shutdown a nodemanager where a container is running.
> - kill the container process.
> - after a while, the container is released by HeartbeatMonitor.
> - Slider AM request a new container to replace that.
> - a new container container is allocated to another nodemanager.
> but, app_container_tag assigned to a new container is greater than the number of component instances (configured by yarn.component.instances)
> i think it does not clear app_container_tag when container is released by HeartbeatMonitor
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)