Uh oh!
There was an error while loading. Please reload this page.
[SPARK-15992] [MESOS] Refactor MesosCoarseGrainedSchedulerBackend offer consideration - #13715
Closed
drcrallen wants to merge 2 commits into
Closed
[SPARK-15992] [MESOS] Refactor MesosCoarseGrainedSchedulerBackend offer consideration#13715drcrallen wants to merge 2 commits into
drcrallen wants to merge 2 commits into
Conversation
rxin
commented
Jun 16, 2016
Contributor
Thanks for the pull request, but the refactoring seems to have made it more difficult to read? |
drcrallen
commented
Jun 17, 2016
ContributorAuthor
I broke something in the test suite, evaluating and I'll open this back in a bit |
| def calculateUsableResources(sc: SparkContext, availableCpus: Int, availableMem: Int): | ||
| Option[(Int, Int)] = { | ||
| val desiredMemory = executorMemory(sc) | ||
| val desiredCpu = executorCores(availableCpus) |
Contributor
There was a problem hiding this comment.
I like the idea, but it does make it harder to read. Can we refactor so we can collapse global and resource limits, and introduce like a case class for each condition, where it knows how to verify and logs error message when it doesn't match?
I think it makes adding and understanding how offers are matched better.
ContributorAuthor
There was a problem hiding this comment.
I can do that. Will be a few weeks before I can tackle this again though.
tnachen
commented
Jun 22, 2016
Contributor
ok to test |
SparkQA
commented
Jun 22, 2016
Test build #60997 has finished for PR 13715 at commit
|
HyukjinKwon
commented
Feb 9, 2017
Member
(ping @drcrallen) |
zifeif2 pushed a commit
to zifeif2/spark
that referenced
this pull request
Nov 22, 2025
## What changes were proposed in this pull request? This PR proposes to close stale PRs. What I mean by "stale" here includes that there are some review comments by reviewers but the author looks inactive without any answer to them more than a month. I left some comments roughly a week ago to ping and the author looks still inactive in these PR below These below includes some PR suggested to be closed and a PR against another branch which seems obviously inappropriate. Given the comments in the last three PRs below, they are probably worth being taken over by anyone who is interested in it. Closesapache#7963Closesapache#8374Closesapache#11192Closesapache#11374Closesapache#11692Closesapache#12243Closesapache#12583Closesapache#12620Closesapache#12675Closesapache#12697Closesapache#12800Closesapache#13715Closesapache#14266Closesapache#15053Closesapache#15159Closesapache#15209Closesapache#15264Closesapache#15267Closesapache#15871Closesapache#15861Closesapache#16319Closesapache#16324Closesapache#16890Closesapache#12398Closesapache#12933Closesapache#14517 ## How was this patch tested? N/A Author: hyukjinkwon <gurwls223@gmail.com> Closesapache#16937 from HyukjinKwon/stale-prs-close.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The offer acceptance workflow is a little hard to follow and not very extensible for future considerations for offers. This is a patch that makes the workflow a little more explicit in its handling of offer resources.