Support MADV_DONTNEED - OTP28
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 54
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
See https://github.com/erlang/otp/pull/10113
Once Riak is upgraded to OTP28, there should be a (default) configuration option to run with OTP memory allocators with MADV_DONTNEED not MADV_FREE.
There have been historic issues in Riak with false reporting of memory leaks, as using MADV_FREE may lead to the OS incorrectly reporting memory as being owned by the beam process when in fact it has been released.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading OTP PR 10113 and the Riak configuration paths that control OTP memory allocators. Determine where a default allocator option can be exposed after the OTP28 upgrade, then verify that selecting MADV_DONTNEED avoids the reported memory-ownership behavior while preserving the existing default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- backend, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100