Skip to content

Conversation

@glentakahashi
Copy link

@glentakahashi glentakahashi commented Aug 16, 2017

Merge Spark-21447

inprogress history file in some cases.

Add failure handling for EOFException that can be thrown during
decompression of an inprogress spark history file, treat same as case
where can't parse the last line.

## What changes were proposed in this pull request?

Failure handling for case of EOFException thrown within the ReplayListenerBus.replay method to handle the case analogous to json parse fail case.  This path can arise in compressed inprogress history files since an incomplete compression block could be read (not flushed by writer on a block boundary).  See the stack trace of this occurrence in the jira ticket (https://issues.apache.org/jira/browse/SPARK-21447)

## How was this patch tested?

Added a unit test that specifically targets validating the failure handling path appropriately when maybeTruncated is true and false.

Author: Eric Vandenberg <ericvandenberg@fb.com>

Closes apache#18673 from ericvandenbergfb/fix_inprogress_compr_history_file.
@ash211
Copy link

ash211 commented Aug 17, 2017

This is subsumed by #247

Generally we try to fully resync from Apache upstream when needing to pull in a commit, as otherwise it's tricky to ensure no commits get dropped in the resync process.

@ash211 ash211 closed this Aug 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants