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 26024200CF1 for ; Mon, 28 Aug 2017 09:39:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 2470B163F8A; Mon, 28 Aug 2017 07:39:07 +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 6A8C5163F78 for ; Mon, 28 Aug 2017 09:39:06 +0200 (CEST) Received: (qmail 55638 invoked by uid 500); 28 Aug 2017 07:39:05 -0000 Mailing-List: contact issues-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@spark.apache.org Received: (qmail 55629 invoked by uid 99); 28 Aug 2017 07:39:04 -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, 28 Aug 2017 07:39:04 +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 92A491A2B5E for ; Mon, 28 Aug 2017 07:39:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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-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 T61NB-KUAutN for ; Mon, 28 Aug 2017 07:39:03 +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 319225FCCB for ; Mon, 28 Aug 2017 07:39:03 +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 89B09E0A32 for ; Mon, 28 Aug 2017 07:39: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 857142538A for ; Mon, 28 Aug 2017 07:39:00 +0000 (UTC) Date: Mon, 28 Aug 2017 07:39:00 +0000 (UTC) From: "Apache Spark (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (SPARK-21568) ConsoleProgressBar should only be enabled in shells MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 28 Aug 2017 07:39:07 -0000 [ https://issues.apache.org/jira/browse/SPARK-21568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-21568: ------------------------------------ Assignee: (was: Apache Spark) > ConsoleProgressBar should only be enabled in shells > --------------------------------------------------- > > Key: SPARK-21568 > URL: https://issues.apache.org/jira/browse/SPARK-21568 > Project: Spark > Issue Type: Bug > Components: Spark Core > Affects Versions: 2.2.0 > Reporter: Marcelo Vanzin > Priority: Minor > > This is the current logic that enables the progress bar: > {code} > _progressBar = > if (_conf.getBoolean("spark.ui.showConsoleProgress", true) && !log.isInfoEnabled) { > Some(new ConsoleProgressBar(this)) > } else { > None > } > {code} > That is based on the logging level; it just happens to align with the default configuration for shells (WARN) and normal apps (INFO). > But if someone changes the default logging config for their app, this may break; they may silence logs by setting the default level to WARN or ERROR, and a normal application will see a lot of log spam from the progress bar (which is especially bad when output is redirected to a file, as is usually done when running in cluster mode). > While it's possible to disable the progress bar separately, this behavior is not really expected. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org For additional commands, e-mail: issues-help@spark.apache.org