Large file upload reports a failed part only after all other parts finish
维护者通常 3 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start in core/src/main/java/com/backblaze/b2/client/B2LargeFileStorer.java at storePartsAsync, where the allOf(...) near line 361 waits for every part. Compare how B2LargeFileUploader.java (around lines 249-251) cancels the remaining futures when one fails. Done when a failing part cancels its siblings and the error surfaces without waiting for slow parts, which a test with one failing and one slow part storer can show.
由索引模型根据 Issue 内容生成。
描述
What happens
B2LargeFileStorer.storePartsAsync() waits for every part with CompletableFuture.allOf, which only completes after all part futures are done, and it does not cancel the remaining parts when one fails. If a part fails early, the caller keeps waiting while the other parts upload to the end, then gets the error. B2LargeFileUploader handles this differently and cancels the other futures when one fails.
Where
core/src/main/java/com/backblaze/b2/client/B2LargeFileStorer.java:361 (allOf(...) in storePartsAsync); compare core/src/main/java/com/backblaze/b2/client/B2LargeFileUploader.java:249-251, which calls cancel(true) on the remaining futures.
Why it matters
Impact: Wrong request or result (the error is delayed and bandwidth is spent on a file that cannot be finished), loud. Severity: High, because it happens on the normal path whenever a part upload fails during a multi-part upload, and the caller has no way to stop the remaining parts early.
How to check
Found by reading the code, not reproduced. Read storePartsAsync: the returned future is built on allOf, and nothing cancels sibling futures or sets the cancellation token on the first failure. A test with one failing part storer and one slow part storer should show the error arriving only after the slow part completes.
Version
Seen at v6.5.0. Present on the default branch: present.
- 主要语言
- Java
- 星标
- 103
- 派生
- 23
- 平均合并
- 5 天 8 小时
- 30 天内合并 PR
- 3
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Backblaze/b2-sdk-java 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
Backblaze/b2-sdk-java#248 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
Backblaze/b2-sdk-java#247 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
Backblaze/b2-sdk-java#246 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
Backblaze/b2-sdk-java#245 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
Backblaze/b2-sdk-java#242 ·
维护者通常 3 天内回复
查看 Backblaze/b2-sdk-java 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
IETF-Hackathon/pqc-certificates#351 ·
维护者通常 2 天内回复
-
bug(core): skip_nodes.json is missing SELECT and PRE, causing Python and Java to insert separators into dropdown options and preformatted text可能已有人在做 @Bhumit267 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
ExceptionThrowShouldUseContext: NullPointerException on a catch block inside an annotation type可能已有人在做 @Carbon14-48 今天认领。 未关闭approved
难度 2/5 1-3 小时 新手友好度 72/100
checkstyle/checkstyle#22784 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复