[
https://issues.apache.org/jira/browse/HDFS-17631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoqiao He updated HDFS-17631:
-------------------------------
Description:
Now when EditLogInputStream.skipUntil() throw IOException in
RedundantEditLogInputStream.nextOp(), it is still into State.OK rather than
State.STREAM_FAILED.
The proper state will be like blew:
State.SKIP_UNTIL -> State.STREAM_FAILED ->(try next stream) State.SKIP_UNTIL
Environment: (was: Now when EditLogInputStream.skipUntil() throw
IOException in RedundantEditLogInputStream.nextOp(), it is still into State.OK
rather than State.STREAM_FAILED.
The proper state will be like blew:
State.SKIP_UNTIL -> State.STREAM_FAILED ->(try next stream) State.SKIP_UNTIL)
> RedundantEditLogInputStream.nextOp() will be State.STREAM_FAILED when
> EditLogInputStream.skipUntil() throw IOException
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-17631
> URL: https://issues.apache.org/jira/browse/HDFS-17631
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: liuguanghua
> Assignee: liuguanghua
> Priority: Major
> Labels: pull-request-available
>
> Now when EditLogInputStream.skipUntil() throw IOException in
> RedundantEditLogInputStream.nextOp(), it is still into State.OK rather than
> State.STREAM_FAILED.
> The proper state will be like blew:
> State.SKIP_UNTIL -> State.STREAM_FAILED ->(try next stream) State.SKIP_UNTIL
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
