Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17235
We are closing it due to inactivity. please do reopen if you want to push
it forward. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/17235
@yanji84 this PR is not correct, can you close it and open a new one with
only your changes?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user grisaitis commented on the issue:
https://github.com/apache/spark/pull/17235
@klueska it enforces a guaranteed number of GPUs allocated to the task,
like other resource guarantees (e.g. cpu, memory).
The max GPU parameter is not a guarantee; you can specify
"spar
Github user klueska commented on the issue:
https://github.com/apache/spark/pull/17235
Can you give a bit more context on what this new parameter is supposed to
enforce? Maybe it's just the same of the parameter that's confusing me.
---
If your project is set up for it, you can reply
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17235
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 feat
