Return-Path: X-Original-To: apmail-flink-issues-archive@minotaur.apache.org Delivered-To: apmail-flink-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 79AAE18518 for ; Fri, 11 Dec 2015 15:09:11 +0000 (UTC) Received: (qmail 5965 invoked by uid 500); 11 Dec 2015 15:09:11 -0000 Delivered-To: apmail-flink-issues-archive@flink.apache.org Received: (qmail 5911 invoked by uid 500); 11 Dec 2015 15:09:11 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 5875 invoked by uid 99); 11 Dec 2015 15:09:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Dec 2015 15:09:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 17A7F2C1F57 for ; Fri, 11 Dec 2015 15:09:11 +0000 (UTC) Date: Fri, 11 Dec 2015 15:09:11 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FLINK-3134) Make YarnJobManager's allocate call asynchronous MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLINK-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052874#comment-15052874 ] ASF GitHub Bot commented on FLINK-3134: --------------------------------------- GitHub user mxm opened a pull request: https://github.com/apache/flink/pull/1450 [FLINK-3134][yarn] asynchronous YarnJobManager heartbeats - use AMRMClientAsync instead of AMRMClient - handle allocation and startup of containers in callbacks - remove YarnHeartbeat message The AMRMClientAsync uses one thread to communicate with the resource manager and an additional thread to execute the callbacks. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mxm/flink yart-heartbeat-async Alternatively you can review and apply these changes as the patch at: https://github.com/apache/flink/pull/1450.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1450 ---- commit 8ec6d492795801ffc7c76f37a3a3200bbf85f81c Author: Maximilian Michels Date: 2015-12-08T13:35:04Z [FLINK-3134][yarn] asynchronous YarnJobManager heartbeats - use AMRMClientAsync instead of AMRMClient - handle allocation and startup of containers in callbacks - remove YarnHeartbeat message The AMRMClientAsync uses one thread to communicate with the resource manager and an additional thread to execute the callbacks. ---- > Make YarnJobManager's allocate call asynchronous > ------------------------------------------------ > > Key: FLINK-3134 > URL: https://issues.apache.org/jira/browse/FLINK-3134 > Project: Flink > Issue Type: Bug > Components: YARN Client > Affects Versions: 0.10.0, 1.0.0, 0.10.1 > Reporter: Maximilian Michels > Assignee: Maximilian Michels > Fix For: 1.0.0 > > > The {{allocate()}} call is used in the {{YarnJobManager}} to send a heartbeat to the YARN resource manager. This call may block the JobManager actor system for arbitrary time, e.g. if retry handlers are set up within the call to allocate. > I propose to use the {{AMRMClientAsync}}'s callback methods to send heartbeats and update the container information. The API is available for our supported Hadoop versions (2.3.0 and above). > https://hadoop.apache.org/docs/stable/api/org/apache/hadoop/yarn/client/api/async/AMRMClientAsync.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)