Enable nvme-ephemeral volumes in the data-loading namespace
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 48/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- kubernetes
調査の方向性
Start by reading the Kubernetes manifests in data-loading/kubernetes/ and the NVMe version linked in pull request #281. Check how the data-loading namespace permits storage classes and ephemeral volume claims, and verify that a 600Gi request fits the pod's node resources. Done when the loading pod can use nvme-ephemeral for /var/solr while data/ remains on its persistent PVC.
索引モデルが issue の本文から書いたものです。
説明
What we need
The Kubernetes namespace we run the data-loading job in cannot currently create a
generic ephemeral volume
with storageClassName: nvme-ephemeral. We would like it to, so that a NameRes data
load can put its Solr index on node-local NVMe.
(Exact error from kubectl describe pod nameres-loading to be pasted in — it looks
like the namespace is not set up for this storage class, either because the class is
not offered to it or because there is no quota for ephemeral volume claims.)
Why
Building a NameRes backup is, in order: download (network), index (CPU), merge (disk),
optimize (disk), compress (CPU). After the parallelisation work in #278, the two
disk-bound phases dominate — optimize=true alone reads ~130G and writes ~130G in a
single forced merge. Both PVCs currently use storageClassName: basic, so the index
lives on network storage, and no amount of tuning in the Makefile substitutes for the
volume being fast.
Node-local NVMe is the single biggest remaining lever on how long a load takes.
Why ephemeral specifically, and why only one of the two volumes
The loading pod mounts two volumes, and they want opposite things:
/var/solr, the index. Takes the entire write load of the indexing run and then
the read-and-write of the optimize, so it benefits most from being fast. It is also
pure intermediate state: oncesnapshot.backup.tar.gzexists the index is worthless,
and if it were lost it could be rebuilt from the synonym files sitting on the other
volume. This is the one we want on NVMe, and ephemeral is the honest lifetime for it.data/, the working directory. Holds the ~130G download and the finished backup
tarball — the only thing the whole exercise produces. Stays on a persistent PVC.
Sizing
The request is 400Gi, which needs to fit on a single node's local NVMe alongside
the pod's other resources (currently 32 CPU / 128Gi).
400Gi is not padding: optimize=true writes the new single segment before deleting the
old ones, so peak usage is 2–3x the finished index, and the index is ~127Gi today. It
cannot go much below roughly 2x without the optimize step running out of space.
Status
data-loading/kubernetes/ currently uses the ordinary nameres-loading-solr PVC, so
loads work today — just slower through the merge and optimize phases. The NVMe version is ready and waiting in #281, which should not be merged until
this is sorted out.
The request there is 600Gi, not the 400Gi originally sketched: the finished index
grows with each Babel release, and peak usage during the optimize is 2-3x it.
- 主要言語
- Python
- スター
- 5
- フォーク
- 4
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
- Dockerfile または Docker Compose ファイルあり
- プルリクエストのテンプレートなし
- コントリビューションガイドなし
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
NCATSTranslator/NameResolution のほかの issue
-
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
-
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
-
難易度 4/5 3〜5日 初心者へのやさしさ 43/100
-
難易度 3/5 1〜2日 初心者へのやさしさ 66/100
-
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
NCATSTranslator/NameResolution の issue をすべて見る
似ている issue
-
cognition facet:consolidation memory ready size:S
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
メンテナーはふだん 1 日以内に返信
-
proposal
難易度 1/5 1時間未満 初心者へのやさしさ 68/100
j3ko/agent-plugins#29 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 80/100
-
area:cli area:security bug priority:medium
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 74/100
Gathin23/cleanyourtv#4026 ·
メンテナーはふだん 1 日以内に返信