Return-Path: X-Original-To: apmail-reef-dev-archive@minotaur.apache.org Delivered-To: apmail-reef-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0461919B26 for ; Wed, 23 Mar 2016 18:04:26 +0000 (UTC) Received: (qmail 7709 invoked by uid 500); 23 Mar 2016 18:04:25 -0000 Delivered-To: apmail-reef-dev-archive@reef.apache.org Received: (qmail 7669 invoked by uid 500); 23 Mar 2016 18:04:25 -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 7575 invoked by uid 99); 23 Mar 2016 18:04:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Mar 2016 18:04:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 82E3C2C14F6 for ; Wed, 23 Mar 2016 18:04:25 +0000 (UTC) Date: Wed, 23 Mar 2016 18:04:25 +0000 (UTC) From: "Ashvin (JIRA)" To: dev@reef.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (REEF-1274) Add validation to YarnConfigurationConstructor 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/REEF-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208886#comment-15208886 ] Ashvin commented on REEF-1274: ------------------------------ Early detection and reporting will be very useful. I think the use cases listed above will cover most scenarios. I have one other use cases. I am not sure if the use cases need separate discussion/jira threads. Many yarn app developers use {{MiniYarnCluster}} to unit test the application. In this case the RM address address in generated at runtime. Which means the address is not part of a config file in classpath. I am wondering if the test RM address could be provided as a configuration to {{YarnConfigurationConstructor}}. > Add validation to YarnConfigurationConstructor > ---------------------------------------------- > > Key: REEF-1274 > URL: https://issues.apache.org/jira/browse/REEF-1274 > Project: REEF > Issue Type: New Feature > Components: REEF-Runtime-YARN > Reporter: Markus Weimer > > A frequent problem REEF applications encounter is a broken or unavailable YARN Configuration of the cluster. REEF can help with the diagnose of such issues as we always load / instantiate the YARN Configuration via {{o..r.runtime.yarn.util.YarnConfigurationConstructor}}. In that class, we can validate the YARN configuration and report WARNINGs into the log if something is odd. For example: > * Is the RM IP set and reachable? > * Is the classpath set and non-empty? If not, are the environment variables set? > * Can a `FileSystem` instance be created using that configuration? > There are probably more tests we can perform as we hear from our users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)