Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18308
There is no cheaper call you can make. Which is the problem here. So either
you have to modify the code so that it keeps track of why the executor has
timed out (i.e. more state being passed around), or you need to tweak the
message so that it says that the timeout is different when there are cached
blocks on the executor.
I'm not so sure there's a lot to gain from printing the exact timeout value
in this message, so I'm leaning towards just tweaking the message a little bit
(e.g. add "or $otherTimeout ms if executor had cached blocks"), or even not
doing anything.
---
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]
