vllm-project / vllm-project/aibrix

local testing with Redis throw TTL not supported by local storage

Open
#2,332 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
5.1k
Forks
694
Avg merge
1d 19h
Merged PRs (30d)
98

Description

### 🐛 Describe the bug

```
2026-06-12 01:08:36,733 - adapter.py:286 - finalize_job_output_data - INFO - {"job_id": "f93f373d-69bb-4fe5-8e93-458275253bfb", "launched": 500, "total": 500, "event": "Finalizing job output data using metastore keys", "logger": "aibrix.batch.storage.adapter", "level": "info", "timestamp": "2026-06-12 08:08:36 UTC"}
```

### Steps to Reproduce

```
kubectl port-forward svc/redis 6379:6379
kubectl port-forward svc/minio 9005:9000 9001:9001

npm run dev
./bin/console --dev-mode -v=2

poetry run python -m aibrix.metadata.app --host 0.0.0.0 --port 8090 --enable-k8s-support

```

### Expected behavior

it should not have such warnings

### Environment

nightly

Contributor guide

Open the contributing guide

Research direction

Start at adapter.py around line 286 and inspect how job output finalization handles Redis TTL with local storage. Reproduce the warning using the listed kubectl, npm, console, and Poetry commands, then confirm the local-storage path no longer emits the unsupported-TTL warning.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, redis
Domain
backend, databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.