[
https://issues.apache.org/jira/browse/TEZ-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706230#comment-14706230
]
Hitesh Shah commented on TEZ-2687:
----------------------------------
bq. Any difference between sleeping before and after ats events flushed to ATS
? Do you concern about the DAGClient ?
Consider a test which wants to verify that containers are released but also at
the same time verify that the data is being pushed into timeline. No real
functional concern apart from the fact that it would be better to finish all
the real work as soon as possible and then wait instead of waiting first.
> ATS History shutdown happens before the min-held containers are released
> ------------------------------------------------------------------------
>
> Key: TEZ-2687
> URL: https://issues.apache.org/jira/browse/TEZ-2687
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.6.2, 0.8.0, 0.7.1
> Reporter: Gopal V
> Assignee: Jeff Zhang
> Attachments: TEZ-2687-1.patch, TEZ-2687-2.patch, TEZ-2687-3.patch,
> TEZ-2687-4.patch, TEZ-2687-6.patch, TEZ-2687-7.patch
>
>
> When ATS goes into a GC pause under heavy loads and while it recovers, each
> Tez AM holds onto a few containers even though it is shutting down and will
> never accept any more DAGs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
