You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by Sunil Parmar <sp...@threatmetrix.com> on 2016/06/03 23:17:58 UTC
Container killed with exit code 105 /143
Still ramping myself up for Apex so apologies for naïve question.
My app runs fine on cluster 1 but when I deployed the same app on cluster
2, I noticed that once app starts yarn assigns 9 containers to it. But
soon in a minute or so all container gets killed. In DataTorrent RTS ui, I
see the following when I hit the details button in the StramEvents tail
window. The steam events says.
StopContainer ID 0000003 exitStatus: -105 [detailsbutton]
Container killed by the ApplicationMaster.
Container killed on request. Exit code is 143
Container exited with a non-zero exit code 143
I think I have configured yarn for enough resources. My set up uses CDH
5.7.
-Sunil
Re: Container killed with exit code 105 /143
Posted by Ashwin Chandra Putta <as...@gmail.com>.
Hey no worries Sunil. Seems like the application master killed the
containers for the operator because it might not have received the
heartbeats for some time. This typically happens if the windows are not
moving forward in the container. Can you check the app master logs if the
heartbeats are being received from the containers?
Regards,
Ashwin.
On Fri, Jun 3, 2016 at 4:17 PM, Sunil Parmar <sp...@threatmetrix.com>
wrote:
> Still ramping myself up for Apex so apologies for naïve question.
>
> My app runs fine on cluster 1 but when I deployed the same app on cluster
> 2, I noticed that once app starts yarn assigns 9 containers to it. But
> soon in a minute or so all container gets killed. In DataTorrent RTS ui, I
> see the following when I hit the details button in the StramEvents tail
> window. The steam events says.
>
>
>
> StopContainer ID 0000003 exitStatus: -105 [detailsbutton]
>
> Container killed by the ApplicationMaster.
> Container killed on request. Exit code is 143
> Container exited with a non-zero exit code 143
>
>
> I think I have configured yarn for enough resources. My set up uses CDH
> 5.7.
>
> -Sunil
>
>
--
Regards,
Ashwin.
Re: Container killed with exit code 105 /143
Posted by Ashwin Chandra Putta <as...@gmail.com>.
Hey no worries Sunil. Seems like the application master killed the
containers for the operator because it might not have received the
heartbeats for some time. This typically happens if the windows are not
moving forward in the container. Can you check the app master logs if the
heartbeats are being received from the containers?
Regards,
Ashwin.
On Fri, Jun 3, 2016 at 4:17 PM, Sunil Parmar <sp...@threatmetrix.com>
wrote:
> Still ramping myself up for Apex so apologies for naïve question.
>
> My app runs fine on cluster 1 but when I deployed the same app on cluster
> 2, I noticed that once app starts yarn assigns 9 containers to it. But
> soon in a minute or so all container gets killed. In DataTorrent RTS ui, I
> see the following when I hit the details button in the StramEvents tail
> window. The steam events says.
>
>
>
> StopContainer ID 0000003 exitStatus: -105 [detailsbutton]
>
> Container killed by the ApplicationMaster.
> Container killed on request. Exit code is 143
> Container exited with a non-zero exit code 143
>
>
> I think I have configured yarn for enough resources. My set up uses CDH
> 5.7.
>
> -Sunil
>
>
--
Regards,
Ashwin.