Skip to content

Conversation

@tmagrino
Copy link
Contributor

What changes were proposed in this pull request?

Previously, the TaskLocation implementation would not allow for executor ids which include underscores. This tweaks the string split used to get the hostname and executor id, allowing for underscores in the executor id.

This addresses the JIRA found here: https://issues.apache.org/jira/browse/SPARK-16148

How was this patch tested?

Ran existing unit tests for core and streaming. Manually ran a simple streaming job with an executor whose id contained underscores and confirmed that the job ran successfully.

This is my original work and I license the work to the project under the project's open source license.

tmagrino added 2 commits June 22, 2016 11:15
Also updated the comment to indicate the string format which includes
the executor id.
@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@srowen
Copy link
Member

srowen commented Jun 22, 2016

This is opened against 1.6, not master. This could be my ignorance, but, why does an executor ID ever have underscores?

@tejasapatil
Copy link
Contributor

@srowen : Since there is a pluggable cluster manager (CM) support in Spark, it is possible to use CM apart from YARN or Mesos.... which can follow its own naming convention for executors. Spark should not be depending on the naming format of executors.

@tmagrino
Copy link
Contributor Author

Closing this and making a new PR against master.

@tmagrino tmagrino closed this Jun 22, 2016
if (hstr.equals(str)) {
if (str.startsWith(executorLocationTag)) {
val splits = str.split("_")
val splits = str.split("_", 3)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, probably even more robust to just use stripPrefix here? this whole method could be a little clearer anyway

asfgit pushed a commit that referenced this pull request Jun 28, 2016
… Executor ID

## What changes were proposed in this pull request?

Previously, the TaskLocation implementation would not allow for executor ids which include underscores.  This tweaks the string split used to get the hostname and executor id, allowing for underscores in the executor id.

This addresses the JIRA found here: https://issues.apache.org/jira/browse/SPARK-16148

This is moved over from a previous PR against branch-1.6: #13857

## How was this patch tested?

Ran existing unit tests for core and streaming.  Manually ran a simple streaming job with an executor whose id contained underscores and confirmed that the job ran successfully.

This is my original work and I license the work to the project under the project's open source license.

Author: Tom Magrino <[email protected]>

Closes #13858 from tmagrino/fixtasklocation.
asfgit pushed a commit that referenced this pull request Jun 28, 2016
… Executor ID

## What changes were proposed in this pull request?

Previously, the TaskLocation implementation would not allow for executor ids which include underscores.  This tweaks the string split used to get the hostname and executor id, allowing for underscores in the executor id.

This addresses the JIRA found here: https://issues.apache.org/jira/browse/SPARK-16148

This is moved over from a previous PR against branch-1.6: #13857

## How was this patch tested?

Ran existing unit tests for core and streaming.  Manually ran a simple streaming job with an executor whose id contained underscores and confirmed that the job ran successfully.

This is my original work and I license the work to the project under the project's open source license.

Author: Tom Magrino <[email protected]>

Closes #13858 from tmagrino/fixtasklocation.

(cherry picked from commit ae14f36)
Signed-off-by: Shixiong Zhu <[email protected]>
asfgit pushed a commit that referenced this pull request Jun 28, 2016
… Executor ID

## What changes were proposed in this pull request?

Previously, the TaskLocation implementation would not allow for executor ids which include underscores.  This tweaks the string split used to get the hostname and executor id, allowing for underscores in the executor id.

This addresses the JIRA found here: https://issues.apache.org/jira/browse/SPARK-16148

This is moved over from a previous PR against branch-1.6: #13857

## How was this patch tested?

Ran existing unit tests for core and streaming.  Manually ran a simple streaming job with an executor whose id contained underscores and confirmed that the job ran successfully.

This is my original work and I license the work to the project under the project's open source license.

Author: Tom Magrino <[email protected]>

Closes #13858 from tmagrino/fixtasklocation.

(cherry picked from commit ae14f36)
Signed-off-by: Shixiong Zhu <[email protected]>
zzcclp pushed a commit to zzcclp/spark that referenced this pull request Jun 29, 2016
… Executor ID

## What changes were proposed in this pull request?

Previously, the TaskLocation implementation would not allow for executor ids which include underscores.  This tweaks the string split used to get the hostname and executor id, allowing for underscores in the executor id.

This addresses the JIRA found here: https://issues.apache.org/jira/browse/SPARK-16148

This is moved over from a previous PR against branch-1.6: apache#13857

## How was this patch tested?

Ran existing unit tests for core and streaming.  Manually ran a simple streaming job with an executor whose id contained underscores and confirmed that the job ran successfully.

This is my original work and I license the work to the project under the project's open source license.

Author: Tom Magrino <[email protected]>

Closes apache#13858 from tmagrino/fixtasklocation.

(cherry picked from commit ae14f36)
Signed-off-by: Shixiong Zhu <[email protected]>
(cherry picked from commit 0cb06c9)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants