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

Abierto
  • ¿Algo no está bien?
#103 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, databases, security

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
1
Forks
1
Merge medio
6 h 45 min
PR fusionados (30 d)
66

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de VectorInstitute/tabctx

Todos los issues de VectorInstitute/tabctx

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.