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.
Sql cli progress bar #4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Sql cli progress bar #4
Changes from 1 commit
17881a4da0761593d3ab87a1a5db866b7df314e70f8c121b0f399d6594798872be5286ed8a260ed73ed8d7c7e379535776390e6bd11604570d589f4b2ed6d0047bff0fa36966b3c2d73a93b9960a72dbabd7510bc49abf8af2d3d018daa37ee8d66192a0877c3731235c71304dcdc9a894fc0e3c88124af8d5957c0e9f9f4d239381ffa6270ec0355afd70a0bcf07cb418f7dcd0983af2a629e5d6532c7b9428322bd87317fb17f5b5bc3e1f372d1c582509bb04407126ad8f865b603d823e3d31f50a58f5118f8361583d150d493308ae288ce796228fc043eefcc7d0823aec6502c66d6e28f2f77dcfcb389b8c81e1a216646b3e1846b0288fc8dbe0efd2144627562688faea2aa966176b69693200110c6bd3bdb7262a0f3d744366829151d2917240840f5f6cd61525c569990a2bee751bc66c178a5d42cf458a926e4883ae33a3a42b35a55a5aaec55cd0a95eb0be4d8254e50f02f888741018bdcc1ef1d6c82f25f56e5b4bfdca8380384899992dd7c91a9de8c4398dfa0bd7a3d1881caa64fe1926dbfa2bf5f05d5fd308ad830e635abf759afdbded396a3445505693c3228732a3357dfa6bdea3ef1af43789a4ab0d99d7e17857f9d4c6ec6f14061c19a10593858e94c992716a2081ae775fae4d50f8df4806cc500039ccab04899b5cb9abf5b345cfd6953314bc2a224efa430388b7a94284c82d59ca478df532595cdb0a94a4fce170422730388baf70542ff39c92cfb1706a1310313c4e619ab0890bf2d71f5b8cb52a1c46bd98097b7ea6030ef8f7f4d58e280ce6dfaa0784f11544ca31b42e74dba38f4e59eccae13bbab2bbd2bca8fdb528e4cd9ccdc2330a56f35f352d0bf447ffd435bdbed4c7705fc6a3d7359a3c8b360afe70b3843224e976946a3228d724847f733f76bd4ddf831553fd83aed44926d1a673af86a1b92f8e4d0a0e63b68629597d5b92b240b1f4dc3f17fad69ed9a48f6478d0800fc43d9c7eFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
…esourceProfile they are created with ### What changes were proposed in this pull request? This is the second PR for the Stage Level Scheduling. This is adding in the necessary executor side changes: 1) executors to know what ResourceProfile they should be using 2) handle parsing the resource profile settings - these are not in the global configs 3) then reporting back to the driver what resource profile it was started with. This PR adds all the piping for YARN to pass the information all the way to executors, but it just uses the default ResourceProfile (which is the global applicatino level configs). At a high level these changes include: 1) adding a new --resourceProfileId option to the CoarseGrainedExecutorBackend 2) Add the ResourceProfile settings to new internal confs that gets passed into the Executor 3) Executor changes that use the resource profile id passed in to read the corresponding ResourceProfile confs and then parse those requests and discover resources as necessary 4) Executor registers to Driver with the Resource profile id so that the ExecutorMonitor can track how many executor with each profile are running 5) YARN side changes to show that passing the resource profile id and confs actually works. Just uses the DefaultResourceProfile for now. I also removed a check from the CoarseGrainedExecutorBackend that used to check to make sure there were task requirements before parsing any custom resource executor requests. With the resource profiles this becomes much more expensive because we would then have to pass the task requests to each executor and the check was just a short cut and not really needed. It was much cleaner just to remove it. Note there were some changes to the ResourceProfile, ExecutorResourceRequests, and TaskResourceRequests in this PR as well because I discovered some issues with things not being immutable. That api now look like: val rpBuilder = new ResourceProfileBuilder() val ereq = new ExecutorResourceRequests() val treq = new TaskResourceRequests() ereq.cores(2).memory("6g").memoryOverhead("2g").pysparkMemory("2g").resource("gpu", 2, "/home/tgraves/getGpus") treq.cpus(2).resource("gpu", 2) val resourceProfile = rpBuilder.require(ereq).require(treq).build This makes is so that ResourceProfile is immutable and Spark can use it directly without worrying about the user changing it. ### Why are the changes needed? These changes are needed for the executor to report which ResourceProfile they are using so that ultimately the dynamic allocation manager can use that information to know how many with a profile are running and how many more it needs to request. Its also needed to get the resource profile confs to the executor so that it can run the appropriate discovery script if needed. ### Does this PR introduce any user-facing change? No ### How was this patch tested? Unit tests and manually on YARN. Closes apache#26682 from tgravescs/SPARK-29306. Authored-by: Thomas Graves <tgraves@nvidia.com> Signed-off-by: Thomas Graves <tgraves@apache.org>Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Uh oh!
There was an error while loading. Please reload this page.