Status: Patch Available
Affects Version/s: 0.20-append, 0.21.1, 0.22.0
Fix Version/s: None
The SequenceFile.Reader api should give the user an easy way to distinguish between a Network/Low-level IOE and a Parsing IOE. The use case appeared recently in the HBase project:
Originally, if a RegionServer got an IOE from HDFS while opening a region file, it would abort the open and let the HMaster reassign the region. The assumption being that this is a network failure that will likely disappear at a later time or different partition of the network. However, if HBase gets parsing exceptions, we want to log the problem and continue opening the region anyways, because parsing is an idempotent problem and retries won't fix this issue.
Although this problem was found in HBase, it seems to be a generic problem of being able to more easily identify idempotent vs transient errors.
|Status||Open [ 1 ]||Patch Available [ 10002 ]|
|Fix Version/s||0.22.0 [ 12314296 ]|
|Fix Version/s||0.20-append [ 12315102 ]|
|Fix Version/s||0.21.1 [ 12315270 ]|