Cache and retention controls: delete, time limits, per-tenant budgets

未关闭
  • 哪里不对？
#103 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
backend, databases, security

调研方向

Start by reading the API and cache management entry points for dataset contexts, uploads, and GPU, host, and spill storage; the issue does not name specific files or tests. Map how contexts are admitted and evicted before working through delete, expiry, tenant budgets, and listing. Done means the stated deletion, expiry, and per-tenant eviction criteria pass, with a retention page documenting storage and restart behavior.

由索引模型根据 Issue 内容生成。

描述

area/api area/memory enhancement P1 roadmap

Users can't control or see how long their data stays on the server. Today a context lives until LRU eviction, can sit in the spill tier on disk, and nothing in the API removes it. Hospitals, banks and similar users need this answered before they deploy. Prior Labs documents none of it.

Add

  • Delete: DELETE /v1/tabctx/datasets/{id} removes a context from GPU, host and spill, along with its uploaded table.
  • Time limits: a server-wide maximum age for contexts and uploads, and an optional per-fit ttl_s that can only be shorter.
  • Per-tenant budgets: a cap on cache bytes per tenant, so one tenant can't evict everyone else's contexts.
  • List: GET /v1/tabctx/datasets shows a tenant's contexts with their size, age, expiry and where each one is held (GPU, host or disk).
  • Docs: a short retention page covering what's stored, where, for how long, and what a restart does.

Accept

  • After a delete or an expiry, nothing about that context is left on GPU, in memory or on disk (tested).
  • A tenant over its budget evicts its own contexts first.

Part of #6, which also covers persistent contexts and a catalog.

主要语言
Python
星标
1
派生
1
平均合并
6 小时 45 分钟
30 天内合并 PR
66

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

VectorInstitute/tabctx 的其他 Issue

查看 VectorInstitute/tabctx 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。