Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 28D2A200C29 for ; Tue, 28 Feb 2017 20:42:50 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 275FA160B7E; Tue, 28 Feb 2017 19:42:50 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 70104160B59 for ; Tue, 28 Feb 2017 20:42:49 +0100 (CET) Received: (qmail 64001 invoked by uid 500); 28 Feb 2017 19:42:48 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 63990 invoked by uid 99); 28 Feb 2017 19:42:48 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Feb 2017 19:42:48 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 3C6CCC094B for ; Tue, 28 Feb 2017 19:42:48 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -2.347 X-Spam-Level: X-Spam-Status: No, score=-2.347 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-2.999, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id P3z86D1Ggj97 for ; Tue, 28 Feb 2017 19:42:46 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 120DA5F4E5 for ; Tue, 28 Feb 2017 19:42:46 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 954BEE060F for ; Tue, 28 Feb 2017 19:42:45 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 52D892415C for ; Tue, 28 Feb 2017 19:42:45 +0000 (UTC) Date: Tue, 28 Feb 2017 19:42:45 +0000 (UTC) From: "Arun Suresh (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-6251) Fix Scheduler locking issue introduced by YARN-6216 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 28 Feb 2017 19:42:50 -0000 [ https://issues.apache.org/jira/browse/YARN-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-6251: ------------------------------ Attachment: YARN-6251.001.patch Uploading fix. The deadlock is due to the fact that the {{completeContainer()}} method (used to flush resources of temporary containers created during the update) is called in the AM's allocate thread, which tries to grab the lock on the queue and app... which can be contended for in the reverse order by the Scheduler thread on a NODE_UPDATE at the same time. The proposed solution is: Instead of calling {{completeContainer()}} directly, we send it as an event to the Scheduler to handle.. This will ensure that the Scheduler is the only entity that will have the lock. > Fix Scheduler locking issue introduced by YARN-6216 > --------------------------------------------------- > > Key: YARN-6251 > URL: https://issues.apache.org/jira/browse/YARN-6251 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Arun Suresh > Assignee: Arun Suresh > Fix For: 3.0.0-alpha3 > > Attachments: YARN-6251.001.patch > > > Opening to track a locking issue that was uncovered when running a custom SLS AMSimulator. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org