Vector fails to reload sink with failed events

[tronboto]

A note for the community

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Problem

Vector doesn't successfully reload a sink with failed events when its config is updated.

1. With the configuration below stored in ./vector/vector.yaml, run vector:

docker run --rm --name vector --network host -v ./vector:/etc/vector timberio/vector:0.50.0-debian

2. Send at least 1 message. If you don't do this, the issue doesn't occur.

echo '{"message":1}' | nc localhost 9000

3. Update the http sink config. For example, change the port or set encoding.json.pretty: true.

4. Reload the config

docker kill -s SIGHUP vector

5. It will fail to reload, the logs show only:

2025-10-31T16:48:54.426518Z  INFO vector::signal: Signal received. signal="SIGHUP"
2025-10-31T16:48:54.427235Z  INFO vector::topology::running: Reloading running topology with new configuration.

The following log messages that show after successful reload are not present:

INFO vector::topology::running: Running healthchecks.
INFO vector::topology::running: New configuration loaded successfully.
INFO vector: Vector has reloaded. path=[File("/etc/vector/vector.yaml", Some(Yaml))]

Note: at the start, if an http server is started with:

python -m http.server 9222

then the issue doesn't occur since the events are "sent" successfully (note the method: get in the sink config).

Configuration

sources:
  source_socket:
    type: socket
    address: 0.0.0.0:9000
    mode: tcp
    decoding:
      codec: json


transforms: {}

sinks:
  sink_http:
    type: http
    inputs:
      - source_socket
    uri: http://localhost:9222
    method: get
    encoding:
      codec: json

Version

vector 0.50.0 (x86_64-unknown-linux-gnu 9053198 2025-09-23 14:18:50.944442940)

Debug Output

Example Data

No response

Additional Context

No response

References

No response