You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Yun Tang (JIRA)" <ji...@apache.org> on 2017/06/28 10:14:00 UTC

[jira] [Updated] (SPARK-21239) Support WAL recover in windows

     [ https://issues.apache.org/jira/browse/SPARK-21239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yun Tang updated SPARK-21239:
-----------------------------
    Description: 
When driver failed over, it will read WAL from HDFS by calling WriteAheadLogBackedBlockRDD.getBlockFromWriteAheadLog(), however, it need a dummy local path to satisfy the method parameter requirements, but the path in windows will contain a colon which is not valid for hadoop. I removed the potential driver letter and colon.

I found one email from spark-user ever talked about this bug (https://www.mail-archive.com/user@spark.apache.org/msg55030.html)

  was:
When driver failed over, it will read WAL from HDFS by calling WriteAheadLogBackedBlockRDD.getBlockFromWriteAheadLog(), however, it need a dummy local path to satisfy the method parameter requirements, but the path in windows will contain a colon which is not valid for hadoop. I removed the potential driver letter and colon.

I found one email from spark-user ever talked about [this bug](https://www.mail-archive.com/user@spark.apache.org/msg55030.html)


> Support WAL recover in windows
> ------------------------------
>
>                 Key: SPARK-21239
>                 URL: https://issues.apache.org/jira/browse/SPARK-21239
>             Project: Spark
>          Issue Type: Bug
>          Components: DStreams, Windows
>    Affects Versions: 1.6.3, 2.1.0, 2.1.1, 2.2.0
>            Reporter: Yun Tang
>             Fix For: 2.1.2, 2.2.1
>
>
> When driver failed over, it will read WAL from HDFS by calling WriteAheadLogBackedBlockRDD.getBlockFromWriteAheadLog(), however, it need a dummy local path to satisfy the method parameter requirements, but the path in windows will contain a colon which is not valid for hadoop. I removed the potential driver letter and colon.
> I found one email from spark-user ever talked about this bug (https://www.mail-archive.com/user@spark.apache.org/msg55030.html)



--
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