Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/14659
Yeah its definitely caused by the call in Task to the
Utils.CallerContext.setCurrent(). It seems to be from it using the
ExecutorClassLoader to go try to check the class for the executor and I guess
because ExecutorClassLoader overrides findClass which is called form loadClass
which is called from forName. There must be something slightly different in
the MessageMatcher which I guess is generated on the fly by netty. I guess
loading the remote one must mismatch with the local one.
@srowen do you think we revert this while we figure it out?
---
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
