vectordotdev / vectordotdev/vector
Support reloading when global options change
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
Context
Vector supports being reloaded while running, but not if any global option has been changed.
Change
We should support reloading even if some global option has been changed.
Implementation
This could be as simple as considering everything has changed when any global option has been changed. But complications could arise when global option data_dir is changed regards to https://vector.dev/docs/administration/process-management/#graceful-pipeline-transitioning. Also how log_schema works would require large change.
Motivation
Removing this exception would streamline our reload story, which would in turn simplify our documentation and enhance UX.
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 reviewing the reload behavior for global options and the graceful pipeline transitioning guidance linked in the issue. Determine how changed data_dir and log_schema should behave, then verify that reloading works after any global option changes without breaking those cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100