[ https://issues.apache.org/jira/browse/SPARK-36354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jungtaek Lim resolved SPARK-36354. ---------------------------------- Fix Version/s: 3.1.3 3.2.0 Resolution: Fixed Issue resolved by pull request 33586 [https://github.com/apache/spark/pull/33586] > EventLogFileReaders should not complain in case of no event log files > --------------------------------------------------------------------- > > Key: SPARK-36354 > URL: https://issues.apache.org/jira/browse/SPARK-36354 > Project: Spark > Issue Type: Bug > Components: Spark Core > Affects Versions: 3.1.2, 3.2.0 > Reporter: Dongjoon Hyun > Assignee: Dongjoon Hyun > Priority: Major > Fix For: 3.2.0, 3.1.3 > > > {code} > 21/07/30 07:38:26 WARN FsHistoryProvider: Error while reading new log > s3a://.../eventlog_v2_spark-95b5c736c8e44037afcf152534d08771 > java.lang.IllegalArgumentException: requirement failed: Log directory must > contain at least one event log file! > at scala.Predef$.require(Predef.scala:281) > at > org.apache.spark.deploy.history.RollingEventLogFilesFileReader.files$lzycompute(EventLogFileReaders.scala:216) > {code} > {code} > $ aws s3 ls s3://.../eventlog_v2_spark-95b5c736c8e44037afcf152534d08771/ > 2021-06-26 22:31:40 0 > appstatus_spark-95b5c736c8e44037afcf152534d08771.inprogress > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org