Github user dbtsai commented on the issue:
https://github.com/apache/spark/pull/17786
@mgummelt We tested this in our production env, and it solves our issue.
Since it seems to be a trivial change, I made my judgement. Gonna wait for more
feedback. Thanks.
---
If your project is
Github user dbtsai commented on the issue:
https://github.com/apache/spark/pull/17786
@mgummelt We tested this in our production env, and it solves our issue.
Since it seems to be a trivial change, I made my judgement. Gonna wait for more
feedback.
---
If your project is set up
Github user dgshep commented on the issue:
https://github.com/apache/spark/pull/17786
Fair point. This felt like a succinct way to handle this corner case, but
if it makes sense to harden the offer refusal code instead, I can update.
---
If your project is set up for it, you can
Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/17786
I agree with @mgummelt, maxCores should have reflected user config option.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user mgummelt commented on the issue:
https://github.com/apache/spark/pull/17786
@dbtsai Can we please wait to get a LGTM from one of the active Mesos
contributers (@skonto, @tnachen, myself, etc.) before merging Mesos code?
I would have rather this be solved in the
Github user dbtsai commented on the issue:
https://github.com/apache/spark/pull/17786
Tests are added in a followup PR. https://github.com/apache/spark/pull/17788
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user dbtsai commented on the issue:
https://github.com/apache/spark/pull/17786
LGTM. Merged into master and branch 2.2. Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17786
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76234/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17786
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17786
**[Test build #76234 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76234/testReport)**
for PR 17786 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17786
**[Test build #76234 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76234/testReport)**
for PR 17786 at commit
Github user dbtsai commented on the issue:
https://github.com/apache/spark/pull/17786
Jenkins, ok to test.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so,
Github user dbtsai commented on the issue:
https://github.com/apache/spark/pull/17786
Jenkins, add to whitelist.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17786
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
14 matches
Mail list logo
