This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Attempting to upgrade from vector 0.27.0-distroless-libc to new versions #21976
Labels
type: bug
A code related bug.
A note for the community
Problem
I am attempting to go from vector 0.27.0-distroless-libc to 0.42.0-distroless-libc. Taking an incremental approach from 0.27.0-distroless-libc to 0.33.0-distroless-libc to 0.38.0-distroless-libc to 0.42.0-distroless-libc we notice memory increases along the way.
On version 0.27.0-distroless-libc we saw an average use of 60-80 MiB On version 0.33.0-distroless-libc we saw an average use of 105 MiB
On both versions 0.38.0-distroless-libc and 0.42.0-distroless-libc we saw an average use of 115-125 MiB. Is it expected for memory usage to increase in this manner? Are there any VRL changes that come to mind between these changes that you think I’d have to make?
Version
0.27.0-distroless-libc, 0.33.0-distroless-libc, 0.38.0-distroless-libc, 0.42.0-distroless-libc
Example Data
On version 0.27.0-distroless-libc we saw an average use of 60-80 MiB On version 0.33.0-distroless-libc we saw an average use of 105 MiB
Additional Context
Vector is running on Kubernetes
Here's what vector top shows on 0.42.0-distroless-libc
The text was updated successfully, but these errors were encountered: