Reload transform Issue

[satellite-no]

Strange issue,

I have a transform that points to a .vrl file that is rather large (33KB). Vector "sees" that the file is changed and issues a reload that completes successfully but the transform output doesnt change. If I run a systemctl reload vector the same result. But if I run a systemctl restart vector the output of the transform will be as expected with the .vrl file updates.

Question:
Is there a known size limit to VRL scripts or files in general when reloading vector vs doing a system stop/start?

[pront]

Is there a known size limit to VRL scripts or files in general when reloading vector vs doing a system stop/start?

Hi @satellite-no, no, afaik these files aren't watched at all. Interesting that you are seeing a reload attempt. There's an open issue for this: #9819

[satellite-no]

Well that makes it even more strange. Maybe its my files structure? Im using config directory and under /configs I have 4 directories sources, transforms, sinks, and vrl. I tested and changes in the vrl directory trigger a reload but with this really large file its not reloading even when I manually reload the service.

[ahakipper]

Encountered the same issue: not only does the Vector process fail to detect updates in the VRL script, but even when Vector's configuration is updated, it doesn't load the latest content of the VRL script.