Multi-host RoCE cores exported at 0572fd12 do not start: pinned FlashInfer 7b35510b records proxy ABI 14, the runtime provides 11
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 35/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
調査の方向性
Start with the three ABI constants the report names: helios/native/roce_proxy.c:103, PROXY_ABI at helios/src/execution/roce.rs:23, and the accepted set in open at roce.rs:125. Compare them against the pinned FlashInfer _roce_proxy.c at flashinfer/experimental/b12x/comm/roce/_roce_proxy.c, then extend native_proxy_abi_matches_core_contract (roce.rs:387-390) to compare the vendored proxy with the pinned library's ABI rather than only with PROXY_ABI. Done means a core recording ABI 14 opens on the rebuilt runtime and the new test fails when the pin and vendored proxy diverge. Note that #232 also changes roce.rs but not these constants.
索引モデルが issue の本文から書いたものです。
説明
What happens
A DeepSeek V4.1 Flash core exported with tensor parallelism 3 on three GB10 hosts (one rank per host, RoCE) does not start under the runtime built from the same tree. Every rank loads its weights and allocates its cache, then stops at "Connect RoCE transport":
[ FAILED ] Connect RoCE transport. 0.0s
Error: Execution(Poisoned(Failure { message: "core RoCE kernels use proxy ABI 14, this runtime provides 11", source: None }))
The exporter and the runtime of 0572fd12 disagree on the RoCE proxy ABI:
- c74b613d pins FlashInfer
7b35510b, whoseflashinfer/experimental/b12x/comm/roce/_roce_proxy.cdefinesROCE_ABI_VERSION 14. local-inference-lab/flashinfer c9b42612 ("Route RoCEnante over direct cables with queue-pair lanes, a partner relay and overrun credits", local-inference-lab/flashinfer#81) raised it from 11. The exporter stores the value that library reports as theproxy_abiof the core's transport (flashinfer/experimental/b12x/comm/roce/roce_oneshot.py:1206). - The runtime's vendored proxy still defines
ROCE_ABI_VERSION 11(helios/native/roce_proxy.c:103),PROXY_ABIis 11 (helios/src/execution/roce.rs:23), andopenaccepts only cores that record ABI 9, 10 or 11 (roce.rs:125).
#251 (e774a468) matched the runtime to ABI 11, which the pin of that time, 85ea6e76, and the later 4e977a53 (d095e9e4) both define. c74b613d replaced ead6cfc1 (b3bf45f9), a revision GitHub no longer resolves, so I could not check its ABI. The message of c74b613d says the pinned revision sits "on top of FlashInfer main's RoCE transport changes" and that "cross-host transport has not been retested here".
Why it matters
A multi-host RoCE core exported at 0572fd12 cannot be served by the runtime of 0572fd12. The mismatch is reported only when a rank connects its transport, after the export has completed (9527 s here) and each start has loaded the weights.
Evidence
- Five starts of one core, three ranks each: 13 of the 15 logs contain the message above. The other two, one of rank 0 and one of rank 1, end at the failed "Connect RoCE transport" step (rank 0 also prints a failed "Load tokenizer" line) without the error text. The block above is from a peer rank.
- The core was exported from
f25a0386(#122 on0572fd12) with--compile-headroom 4G, because the default export of0572fd12stops in kernel tuning on these hosts (#270).f25a0386changes no Rust or C source and no dependency pin relative to0572fd12. - The runtime was built from the same tree with
cargo build --release --locked --manifest-path flare-cli/Cargo.toml --features roce. direct_url.jsonof the installedflashinfer-python0.7.3 records commit7b35510b, asuv.lockpins.
Not measured
- Whether ABI 12 to 14 change what the captured kernels see, or only the proxy's own side. The vendored proxy and the pinned FlashInfer's
_roce_proxy.cdiffer in more than the version constant. - Single-host cores and other models. The check runs only where a core records a RoCE transport.
Possible direction
- The repair #251 made for ABI 11: bring
helios/native/roce_proxy.c,PROXY_ABIand the accepted set inopenup to the pinned FlashInfer's ABI 14. #232 (open, "Route multi-host RoCE rails over direct cables") changesroce.rsand does not change these constants. - A test that compares the vendored proxy's
ROCE_ABI_VERSIONwith the one in the pinned FlashInfer, so that a pin that changes the ABI fails in CI.native_proxy_abi_matches_core_contract(roce.rs:387-390) compares the vendored proxy only withPROXY_ABI.
Environment
- Three GB10 hosts (DGX Spark class), one rank per host, RoCE between them.
- Checkpoint
deepseek-ai/DeepSeek-V4.1-Flash-1017. 0572fd12runtime; core exported fromf25a0386; FlashInfer7b35510b.
- 主要言語
- Rust
- スター
- 800
- フォーク
- 106
- 平均マージ
- 1日 3時間
- マージ済み PR(30日)
- 100
環境構築
- Dockerfile または Docker Compose ファイルあり
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
NVIDIA/hyperflare-inference のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
NVIDIA/hyperflare-inference#268 ·
メンテナーはふだん 1 日以内に返信
-
area:caching area:engram enhancement performance triage:design-review
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
NVIDIA/hyperflare-inference#230 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 5/5 1週間以上 初心者へのやさしさ 15/100
NVIDIA/hyperflare-inference#278 ·
メンテナーはふだん 1 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 25/100
NVIDIA/hyperflare-inference#276 ·
メンテナーはふだん 1 日以内に返信
-
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
NVIDIA/hyperflare-inference#270 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
NVIDIA/hyperflare-inference の issue をすべて見る
似ている issue
-
bug UI
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
wardian-app/Wardian#1746 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
jlcodes99/cockpit-tools#3125 ·
メンテナーはふだん 2 日以内に返信
-
bug user-sprint
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
Vondor/KassenSturz#967 ·
メンテナーはふだん 1 日以内に返信
-
area/ci
難易度 1/5 1時間未満 初心者へのやさしさ 62/100
メンテナーはふだん 1 日以内に返信
-
[BUG] Incremental sync warns "no stored highest_uid" on every round for folders with no new mailオープンbug
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
rustmailer/bichon#411 ·