Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/3994#issuecomment-70358204
@jongyoul when you're talking about the spark file, you're talking about
the spark executor uri tar itself right?
The TASK_LOST behavior certainly shouldn't happen normally. The only thing
I can think of is the executor takes longer to launch due to longer time
downloading the file, and executor registration timeout triggered the task to
fail/lost.
Can you repro this behavior with setting verbose logging (env variable
GLOG_v=1) on the slave, and share the logs around when you get the TASK_LOST?
---
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]
