[
https://issues.apache.org/jira/browse/HDFS-17808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18065933#comment-18065933
]
ASF GitHub Bot commented on HDFS-17808:
---------------------------------------
github-actions[bot] commented on PR #7810:
URL: https://github.com/apache/hadoop/pull/7810#issuecomment-4061814839
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> EC: End block group in advance to prevent write failure for long-time running
> OutputStream
> ------------------------------------------------------------------------------------------
>
> Key: HDFS-17808
> URL: https://issues.apache.org/jira/browse/HDFS-17808
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: ec, erasure-coding
> Reporter: Haobo Zhang
> Assignee: Haobo Zhang
> Priority: Major
> Labels: pull-request-available
>
> Recently, we met an EC problem in our production.
> User creates an output stream to write ec files. That output stream writes
> some bytes and will be idle for a long time until data is ready. If we
> restart our cluster's datanodes to version up, those applications will
> finally fail due to not have enough healthy streamers.
>
> This Jira try to solve above problem by end block group in advance when we
> already have failed streamers but less than parity number.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
