Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/10821#issuecomment-194336009
So at this point this isn't really changing anything right? Except not to
set attempt is not in cluster mode? But that was handled by redirect in
history server anyway. Otherwise I'm not following how the attemptId would be
wrong. In cluster mode the attemptid should be set to something. Its getting
it directly from the containerid that is set on your yarn cluster. If you
don't have containerid then I assume you aren't running on yarn or yarn has a
bug.
Which version of hadoop are you using?
Also are you sure the history server just hasn't loaded the file yet?
---
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
