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 天內回覆