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 531AA200C85 for ; Mon, 15 May 2017 23:16:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 51BC0160BA9; Mon, 15 May 2017 21:16:09 +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 96DBC160BC2 for ; Mon, 15 May 2017 23:16:08 +0200 (CEST) Received: (qmail 65730 invoked by uid 500); 15 May 2017 21:16:07 -0000 Mailing-List: contact dev-help@reef.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@reef.apache.org Delivered-To: mailing list dev@reef.apache.org Received: (qmail 65719 invoked by uid 99); 15 May 2017 21:16:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 May 2017 21:16:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 2AA421A0570 for ; Mon, 15 May 2017 21:16:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id J6wUwZkY3TmX for ; Mon, 15 May 2017 21:16:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id AB2745F520 for ; Mon, 15 May 2017 21:16:05 +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 D7020E0D4D for ; Mon, 15 May 2017 21:16:04 +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 208F724394 for ; Mon, 15 May 2017 21:16:04 +0000 (UTC) Date: Mon, 15 May 2017 21:16:04 +0000 (UTC) From: "Sergiy Matusevych (JIRA)" To: dev@reef.apache.org Message-ID: In-Reply-To: References:

Subject: [jira] [Commented] (REEF-1796) All REEF YARN jobs end with FORCE_CLOSED status on the client side MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 15 May 2017 21:16:09 -0000 [ https://issues.apache.org/jira/browse/REEF-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011340#comment-16011340 ] Sergiy Matusevych commented on REEF-1796: ----------------------------------------- Looks like we have a Driver setup issue. I've just noticed the following message in HelloREEF Driver log on YARN: {code} 2017-05-12 14:14:30,346 FINE reef.runtime.common.driver.client.RemoteClientJobStatusHandler. main | Instantiated 'RemoteClientJobStatusHandler' without an actual connection to the client. {code} So it's not that we close the connection prematurely - it is likely we don't have it at all :) > All REEF YARN jobs end with FORCE_CLOSED status on the client side > ------------------------------------------------------------------ > > Key: REEF-1796 > URL: https://issues.apache.org/jira/browse/REEF-1796 > Project: REEF > Issue Type: Bug > Reporter: Sergiy Matusevych > Priority: Critical > Labels: bug, yarn > Original Estimate: 336h > Remaining Estimate: 336h > > It looks like the connection between REEF driver and REEF client is being closed prematurely either on the client or on the driver side when using YARN runtime. As a result, REEF driver fails to communicate its final status to the client, and the client times out with {{FORCE_CLOSED}} status. That causes *all* unit tests to fail on YARN. From the logs it can be seen that REEF jobs complete normally on YARN; it's just the final status message that does not make it to the client. > To reproduce: run e.g. HelloREEF application on YARN, > {code} > .\bin\runreef.ps1 -VerboseLog -Jars .\lang\java\reef-examples\target\reef-examples-0.16.0-SNAPSHOT-shaded.jar -Class org.apache.reef.examples.hello.HelloREEFYarn > {code} > or run unt tests > {code} > .\bin\runtests.ps1 -Yarn -Jars ".\lang\java\reef-examples\target\reef-examples-0.16.0-SNAPSHOT-shaded.jar;.\lang\java\reef-tests\target\reef-tests-0.16.0-SNAPSHOT-test-jar-with-dependencies.jar" > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)