vector: Failed to run on CentOS 8 due to page size differences
Vector Version
0.10.0
Vector Configuration File
Debug Output
Expected Behavior
Vector run on AWS t4g instance
Actual Behavior
Vector fail to run with error
<jemalloc>: Unsupported system page size
memory allocation of 32 bytes failed
Aborted
Example Data
Additional Context
Installed Vector from archive or RPM package on AWS t4g instance (Graviton 2 ARM64) processor. AMI: Centos 8
References
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 20 (12 by maintainers)
Commits related to this issue
- chore(platforms): Pass through jemalloc page size env vars We may or may not end up using these, but it is useful for users that want to build Vector for another platform with a different page size. ... — committed to vectordotdev/vector by jszwedko 2 years ago
- chore(platforms): Pass through jemalloc page size env vars (#10940) We may or may not end up using these, but it is useful for users that want to build Vector for another platform with a different p... — committed to vectordotdev/vector by jszwedko 2 years ago
@jszwedko thank you, that will help with building my own rpm.
That is good to know, thank you @markmartirosian !
Just for reference, in case users want to compile Vector themselves for systems with 64 K page sizes, you can use:
once https://github.com/vectordotdev/vector/pull/10940 is merged.
Ah, doh, I completely forgot about this Centos 8 issue when we re-enabled jemalloc in 0.19.0. I’ll re-open this for tracking.