[
https://issues.apache.org/jira/browse/TEZ-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14204373#comment-14204373
]
Rohini Palaniswamy commented on TEZ-1766:
-----------------------------------------
bq. 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.
Aware of that. There is 40 or 50 retries with backoff I believe. But
you should still make the Tez AM exit at some point. Right now it is hung
forever even after it comes out of the unregister retry loop.
bq. 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.
We have our own TezMiniCluster and do not use the tez one.
> 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)
