[jira] [Issue Comment Deleted] (SPARK-2557) createTaskScheduler should be consistent between local and local-n-failures

["Maximilian Michels (JIRA)" <ji...@apache.org>]

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

Maximilian Michels updated SPARK-2557:
--------------------------------------
    Comment: was deleted

(was: User 'zentol' has created a pull request for this issue:
https://github.com/apache/flink/pull/1045)

> createTaskScheduler should be consistent between local and local-n-failures 
> ----------------------------------------------------------------------------
>
>                 Key: SPARK-2557
>                 URL: https://issues.apache.org/jira/browse/SPARK-2557
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 1.0.0
>            Reporter: Xianjin YE
>            Priority: Minor
>              Labels: starter
>             Fix For: 1.1.0
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> In SparkContext.createTaskScheduler, we can use {code}local[*]{code} to estimates the number of cores on the machine. I think we should also be able to use * in the local-n-failures mode.
> And according to the code in the LOCAL_N_REGEX pattern matching code, I believe the regular expression of LOCAL_N_REGEX is wrong. LOCAL_N_REFEX should be 
> {code}
> """local\[([0-9]+|\*)\]""".r
> {code} 
> rather than
> {code}
>  """local\[([0-9\*]+)\]""".r
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org