Return-Path: X-Original-To: apmail-hive-issues-archive@minotaur.apache.org Delivered-To: apmail-hive-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 0A01318AEC for ; Wed, 30 Mar 2016 02:23:25 +0000 (UTC) Received: (qmail 19274 invoked by uid 500); 30 Mar 2016 02:23:25 -0000 Delivered-To: apmail-hive-issues-archive@hive.apache.org Received: (qmail 19249 invoked by uid 500); 30 Mar 2016 02:23:25 -0000 Mailing-List: contact issues-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list issues@hive.apache.org Received: (qmail 19227 invoked by uid 99); 30 Mar 2016 02:23:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Mar 2016 02:23:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 9A7762C1F68 for ; Wed, 30 Mar 2016 02:23:25 +0000 (UTC) Date: Wed, 30 Mar 2016 02:23:25 +0000 (UTC) From: "Szehon Ho (JIRA)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HIVE-13376) HoS emits too many logs with application state 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/HIVE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Szehon Ho updated HIVE-13376: ----------------------------- Status: Patch Available (was: Open) [~lirui], [~xuefuz] do you guys have any thoughts about this? Thanks > HoS emits too many logs with application state > ---------------------------------------------- > > Key: HIVE-13376 > URL: https://issues.apache.org/jira/browse/HIVE-13376 > Project: Hive > Issue Type: Improvement > Components: Spark > Reporter: Szehon Ho > Assignee: Szehon Ho > Attachments: HIVE-13376.patch > > > The logs get flooded with something like: > > Mar 28, 3:12:21.851 PM INFO org.apache.hive.spark.client.SparkClientImpl > > [stderr-redir-1]: 16/03/28 15:12:21 INFO yarn.Client: Application report for application_1458679386200_0161 (state: RUNNING) > > Mar 28, 3:12:21.912 PM INFO org.apache.hive.spark.client.SparkClientImpl > > [stderr-redir-1]: 16/03/28 15:12:21 INFO yarn.Client: Application report for application_1458679386200_0149 (state: RUNNING) > > Mar 28, 3:12:22.853 PM INFO org.apache.hive.spark.client.SparkClientImpl > > [stderr-redir-1]: 16/03/28 15:12:22 INFO yarn.Client: Application report for application_1458679386200_0161 (state: RUNNING) > > Mar 28, 3:12:22.913 PM INFO org.apache.hive.spark.client.SparkClientImpl > > [stderr-redir-1]: 16/03/28 15:12:22 INFO yarn.Client: Application report for application_1458679386200_0149 (state: RUNNING) > > Mar 28, 3:12:23.855 PM INFO org.apache.hive.spark.client.SparkClientImpl > > [stderr-redir-1]: 16/03/28 15:12:23 INFO yarn.Client: Application report for application_1458679386200_0161 (state: RUNNING) > While this is good information, it is a bit much. > Seems like SparkJobMonitor hard-codes its interval to 1 second. It should be higher and perhaps made configurable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)