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 4CF76200D10 for ; Sat, 26 Aug 2017 00:16:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4BBDE16D32F; Fri, 25 Aug 2017 22:16:06 +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 94BB216D322 for ; Sat, 26 Aug 2017 00:16:05 +0200 (CEST) Received: (qmail 20016 invoked by uid 500); 25 Aug 2017 22:16:03 -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 20004 invoked by uid 99); 25 Aug 2017 22:16:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Aug 2017 22:16:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 0537A1811B6 for ; Fri, 25 Aug 2017 22:16:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id eSU8ytWr4WQt for ; Fri, 25 Aug 2017 22:16:02 +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 F06145FCB9 for ; Fri, 25 Aug 2017 22:16:01 +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 14A46E0D57 for ; Fri, 25 Aug 2017 22:16:01 +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 582FF25385 for ; Fri, 25 Aug 2017 22:16:00 +0000 (UTC) Date: Fri, 25 Aug 2017 22:16:00 +0000 (UTC) From: "Botong Huang (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-6640) AM heartbeat stuck when responseId overflows MAX_INT MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 25 Aug 2017 22:16:06 -0000 [ https://issues.apache.org/jira/browse/YARN-6640?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16142= 312#comment-16142312 ]=20 Botong Huang commented on YARN-6640: ------------------------------------ Hi [~vinodkv], yes the same issue exists NM->RM hearbeat as well. This's ac= tually in my todo list. Just opened YARN-7102 for it and will work on it so= on. Thanks!=20 > AM heartbeat stuck when responseId overflows MAX_INT > ----------------------------------------------------- > > Key: YARN-6640 > URL: https://issues.apache.org/jira/browse/YARN-6640 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Botong Huang > Assignee: Botong Huang > Priority: Blocker > Fix For: 2.9.0, 3.0.0-beta1, 2.8.2 > > Attachments: YARN-6640.v1.patch, YARN-6640.v2.patch > > > The current code in {{ApplicationMasterService}}:=20 > if ((request.getResponseId() + 1) =3D=3D lastResponse.getResponseId()) {/= * old heartbeat */ return lastResponse;} > else if (request.getResponseId() + 1 < lastResponse.getResponseId()) { th= row ... } > process the heartbeat... > When a heartbeat comes in, in usual case we are expecting request.getResp= onseId() =3D=3D lastResponse.getResponseId(). The =E2=80=9Cif=E2=80=9C is f= or the duplicate heartbeat that=E2=80=99s one step old, the =E2=80=9Celse i= f=E2=80=9D is to throw and complain for heartbeats more than two steps old,= otherwise we accept the new heartbeat and process it. > So the bug is: when lastResponse.getResponseId() =3D=3D MAX_INT, the newe= st heartbeat comes in with responseId =3D=3D MAX_INT. However reponseId + 1= will be MIN_INT, and we will fall into the =E2=80=9Celse if=E2=80=9D case = and RM will throw. Then we are stuck here=E2=80=A6 -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org