Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3527#issuecomment-65022618
Nice catch. I don't think that it's very common to set
`spark.akka.frameSize` these days, since 1.1's task broadcasting should have
addressed the most common causes of messages that exceeded the frame size, but
it certainly doesn't hurt to warn / guard against bad inputs.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
