Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 23 Jan 2015 19:20:34 +0000 (UTC)
From: "Tsuyoshi OZAWA (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12769158.1421884468000.159510.1422040834774@Atlassian.JIRA>
In-Reply-To: <JIRA.12769158.1421884468000@Atlassian.JIRA>
References: <JIRA.12769158.1421884468000@Atlassian.JIRA>
 <JIRA.12769158.1421884468855@arcas>
Subject: [jira] [Commented] (YARN-3081) Potential indefinite wait in
 ContainerManagementProtocolProxy#addProxyToCache()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/YARN-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289773#comment-14289773 ] 

Tsuyoshi OZAWA commented on YARN-3081:
--------------------------------------

Thank you, Ted!

> Potential indefinite wait in ContainerManagementProtocolProxy#addProxyToCache()
> -------------------------------------------------------------------------------
>
>                 Key: YARN-3081
>                 URL: https://issues.apache.org/jira/browse/YARN-3081
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>            Priority: Minor
>         Attachments: yarn-3081-001.patch
>
>
> {code}
>       if (!removedProxy) {
>         // all of the proxies are currently in use and already scheduled
>         // for removal, so we need to wait until at least one of them closes
>         try {
>           this.wait();
> {code}
> The above code can wait for a condition that has already been satisfied, leading to indefinite wait.


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