From issues-return-206011-archive-asf-public=cust-asf.ponee.io@spark.apache.org Fri Oct 26 20:08:03 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 17E74180675 for ; Fri, 26 Oct 2018 20:08:02 +0200 (CEST) Received: (qmail 16124 invoked by uid 500); 26 Oct 2018 18:08:02 -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 16065 invoked by uid 99); 26 Oct 2018 18:08:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Oct 2018 18:08:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id DAC9CC222C for ; Fri, 26 Oct 2018 18:08:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id w8_e2QxfQyGX for ; Fri, 26 Oct 2018 18:08:01 +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 19AB45F531 for ; Fri, 26 Oct 2018 18:08: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 9F585E0E3E for ; Fri, 26 Oct 2018 18:08:00 +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 5D2C126693 for ; Fri, 26 Oct 2018 18:08:00 +0000 (UTC) Date: Fri, 26 Oct 2018 18:08:00 +0000 (UTC) From: "Imran Rashid (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (SPARK-25855) Don't use Erasure Coding for event log files MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Imran Rashid created SPARK-25855: ------------------------------------ Summary: Don't use Erasure Coding for event log files Key: SPARK-25855 URL: https://issues.apache.org/jira/browse/SPARK-25855 Project: Spark Issue Type: Improvement Components: Spark Core Affects Versions: 2.4.0 Reporter: Imran Rashid While testing spark with hdfs erasure coding (new in hadoop 3), we ran into a bug with the event logs. The main issue was a bug in hdfs (HDFS-14027), but it did make us wonder whether Spark should be using EC for event log files in general. Its a poor choice because EC currently implements {{hflush()}} or {{hsync()}} as no-ops, which mean you won't see anything in your event logs until the app is complete. That isn't necessarily a bug, but isn't really great. So I think we should ensure EC is always off for event logs. Also related are SPARK-24787 & SPARK-19531. The space savings from EC would be nice as the event logs can get somewhat large, but I think other factors outweigh this. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org For additional commands, e-mail: issues-help@spark.apache.org