Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1860#issuecomment-53200124
Hey Martin,
I'm having a bit of trouble seeing how this works around the issue. From
what I can tell the issue is that if someone creates Executors that consume all
memory, Mesos will refuse to make offers for the tasks. However, this fix just
adds 32MB of memory as a requirement for the task... but it seems like if the
offer is never made in the first place, this will make no difference. Can you
describe a sequence of offers where this change alters the execution? Thanks
for looking into this!
- Patrick
---
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, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
