vectordotdev / vectordotdev/vector
Save tag_cardinality_limit cache to disk before shutdown
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
Currently, the tag_cardinality_limit transform's cache is held in memory. This means that the cache is reset between Vector restarts. For most cases, this should be sufficient, since this transform is designed as a protection mechanism for long-lived Vector processes. But I could see this being a problem for very large setups where data is continually violating the cardinality limit.
I'm opening this issue for feedback from users. If you find this valuable please comment and 👍 .
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the tag_cardinality_limit transform and its in-memory cache lifecycle, especially how shutdown is handled. The issue is a request for user feedback rather than an implementation plan; done would require an agreed design for saving and restoring the cache across Vector restarts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100