redpanda-data / redpanda-data/redpanda

The hard minimum memory requirement is wrongly presented as "recommended" and non-fatal

Open
#30,172 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/bug
Dominant language
C++
Stars
12.6k
Forks
792
PR merge metrics
No merged PRs in 30d

Description

Version & Environment

Redpanda version: (use rpk version): v26.1.4
OS: Ubuntu 24.04

What went wrong?

If you start Redpanda with not enough memory it fails with an error:

Failure during startup: std::runtime_error (Memory: '...' below recommended: '...')

This is fine, but if it’s a hard requirement then:

  1. it shouldn’t describe the minimum as just "recommended"
  2. the SEVERITY given by rpk redpanda check for the Free memory per CPU [MB] row should be Fatal, not Warning
What should have happened instead?
  1. It should say "below minimum:"
  2. The SEVERITY should be Fatal
How to reproduce the issue?
  1. Start Redpanda on a server with not enough RAM.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the startup memory error that reports memory as "below recommended," then locate the rpk redpanda check implementation for the Free memory per CPU [MB] row. Done means the message says "below minimum" and that row reports Fatal severity; the payload names no files or tests, so search by these exact strings first.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
backend, cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
56/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.