Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attempting to upgrade from vector 0.27.0-distroless-libc to new versions #21976

Closed
mohdAkibUddin opened this issue Dec 6, 2024 · 1 comment
Closed
Labels
type: bug A code related bug.

Comments

@mohdAkibUddin
Copy link

mohdAkibUddin commented Dec 6, 2024

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

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
image

@mohdAkibUddin mohdAkibUddin added the type: bug A code related bug. label Dec 6, 2024
@pront
Copy link
Member

pront commented Dec 6, 2024

Are there any VRL changes that come to mind between these changes that you think I’d have to make?

I would recommend smaller incremental changes. You can follow the upgrade guides (here).

@vectordotdev vectordotdev locked and limited conversation to collaborators Dec 6, 2024
@jszwedko jszwedko converted this issue into discussion #21978 Dec 6, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
type: bug A code related bug.
Projects
None yet
Development

No branches or pull requests

2 participants