Spark history log show IOException Error while a application is running #6489
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… running
After adding SPARK-6197 as a patch to spark-1.3.1, I found it no longer
prints out an Error Exception in history log after a application is
failed. But while a application is running, it may still print out a
IOException Error, like this "ERROR FsHistoryProvider: Failed to load
application log data from
FileStatus{path=hdfs://yarncluster/history/sparkhistory/application_1426843812583_0085.snappy.inprogress;
isDirectory=false; length=270; replication=2; blocksize=134217728;
modification_time=1432797327877; access_time=1432797327877;
owner=hadoop; group=supergroup; permission=rwxrwx---; isSymlink=false}.
java.io.IOException: failed to read chunk"
|
Can one of the admins verify this patch? |
Member
|
No, I don't think this is a valid change. This error is not about an incomplete file, but missing chunks in HDFS. I am not sure what you back-ported where here. Would you close this PR? |
Author
|
Yeah, I agree with Owen this "failed to read chunk" problem is not caused by replaying an unfinished app. But there may be some other reasons for it, this doesn't happen before 1.3.1. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After adding SPARK-6197 as a patch to spark-1.3.1, I found it no longer
prints out an Error Exception in history log after a application is
failed. But while a application is running, it may still print out a
IOException Error, like this:
ERROR FsHistoryProvider: Failed to load application log data from FileStatus{path=hdfs://yarncluster/history/sparkhistory/application_1426843812583_0085.snappy.inprogress; isDirectory=false; length=270; replication=2; blocksize=134217728; modification_time=1432797327877; access_time=1432797327877; owner=hxia; group=supergroup; permission=rwxrwx---; isSymlink=false}.
java.io.IOException: failed to read chunk