[ 
https://issues.apache.org/jira/browse/YARN-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhiyuan Yang updated YARN-5436:
-------------------------------
    Description: In YARN-2264, a race in DrainDispatcher was fixed. 
Unfortunately, it also exists in AsyncDispatcher but wasn't found. In 
YARN-2991, another DrainDispatcher bug was fixed by letting DrainDispatcher 
reuse some AsyncDispatcher method because AsyncDispatcher doesn't have such 
issue. However, this shadows YARN-2264, and now similar race reappears in Tez 
unit tests (probably also YARN unit tests also).  (was: In YARN-2264, a race in 
DrainDispatcher was fixed. Unfortunately, it also exists in AsyncDispatcher but 
wasn't found. In YARN-2991, another DrainDispatcher bug was fixed by letting 
DrainDispatcher extend AsyncDispatcher because AsyncDispatcher doesn't have 
such issue. However, this shadows YARN-2264, and now similar race reappears in 
Tez unit tests (probably also YARN unit tests also).)

> Race in AsyncDispatcher can cause random test failures in Tez(probably YARN 
> also )
> ----------------------------------------------------------------------------------
>
>                 Key: YARN-5436
>                 URL: https://issues.apache.org/jira/browse/YARN-5436
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Zhiyuan Yang
>            Assignee: Zhiyuan Yang
>
> In YARN-2264, a race in DrainDispatcher was fixed. Unfortunately, it also 
> exists in AsyncDispatcher but wasn't found. In YARN-2991, another 
> DrainDispatcher bug was fixed by letting DrainDispatcher reuse some 
> AsyncDispatcher method because AsyncDispatcher doesn't have such issue. 
> However, this shadows YARN-2264, and now similar race reappears in Tez unit 
> tests (probably also YARN unit tests also).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to