Skip to content

Conversation

@xuchenCN
Copy link
Contributor

Issue description SPARK-8374

Application starve because YARN scheduler preemption,we should to keep Running containers number
Do not think about the resource ,that is Yarn scheduler's job .

@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@srowen
Copy link
Member

srowen commented Jun 29, 2015

CC @sryza for a look

@srowen
Copy link
Member

srowen commented Jun 29, 2015

OK to test

@SparkQA
Copy link

SparkQA commented Jun 29, 2015

Test build #978 has started for PR 7083 at commit 9555dd5.

@SparkQA
Copy link

SparkQA commented Jun 29, 2015

Test build #978 has finished for PR 7083 at commit 9555dd5.

  • This patch fails Scala style tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@tgravescs
Copy link
Contributor

@xuchenCN can you add the first "[" to the description before jira number

@sryza
Copy link
Contributor

sryza commented Jun 29, 2015

Hi @xuchenCN what makes you think this is the right fix? We already decrement numExecutorsRunning when a container is killed, so I think doing it again would be double-counting.

@xuchenCN xuchenCN changed the title SPARK-8374] [YARN] Job frequently hangs after YARN preemption [SPARK-8374] [YARN] Job frequently hangs after YARN preemption Jun 30, 2015
@xuchenCN
Copy link
Contributor Author

Thanks @sryza I notice that is mistake, I 'm trying to find way to fix this issue

@xuchenCN xuchenCN closed this Jun 30, 2015
@xuchenCN
Copy link
Contributor Author

PR changes #7128

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.

6 participants