[
https://issues.apache.org/jira/browse/TEZ-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14204364#comment-14204364
]
Hitesh Shah edited comment on TEZ-1766 at 11/10/14 5:28 AM:
------------------------------------------------------------
Yes - the info is sufficient. This is due to the AM-RM interaction when
unregistering the app from the RM. In some cases, the dag sends it completed
status back to the unit test causing the unit test to start shutting down the
cluster way before the AM does its unregister. The default behavior of the AM
is to wait a long time ( a result of the changes that went in to support HA for
the RM ) hoping that the RM will come back so that it can unregister itself.
There probably should be some settings that we can tweak in the MiniTezCluster
configs as well as adding a minimal sleep before the cluster shutdown is
invoked.
was (Author: hitesh):
Yes - the info is sufficient. This is due to the AM-RM interaction when
unregistering the app from the RM. In some cases, the dag sends it completed
status back to the unit test causing the unit test to start shutting down the
cluster before the AM initiates its unregister. The default behavior of the AM
is to wait a long time ( a result of the changes that went in to support HA for
the RM ) hoping that the RM will come back so that it can unregister itself.
There probably should be some settings that we can tweak in the MiniTezCluster
configs as well as adding a minimal sleep before the cluster shutdown is
invoked.
> Running pig unit tests leaks few DAGAppMaster jvms
> --------------------------------------------------
>
> Key: TEZ-1766
> URL: https://issues.apache.org/jira/browse/TEZ-1766
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Rohini Palaniswamy
>
> I see around 3 to 4 org.apache.tez.dag.app.DAGAppMaster processes being
> leaked at the end of each test-tez run in both 5.1 and 5.2 for different
> tests in each run.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
