MariaDB ColumnStore eats all memory and makes the machine unresponsive

Open
  • Is something wrong?
#545 8 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
mariadb
Domain
databases

Research direction

No file or test is named. Start by running the default ClickBench configuration with MariaDB ColumnStore on a c6a.4xlarge with 32 GB RAM, then capture the conditions and memory usage when the machine becomes unresponsive. Done means a reproducible case suitable for the MariaDB team.

Written by the indexing model from the issue text.

Description

On the default ClickBench configuration of c6a.4xlarge (32 GB RAM).

This bug report is for the MariaDB team.

Dominant language
Shell
Stars
1.1k
Forks
328
Avg merge
4h 12m
Merged PRs (30d)
605

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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.

More from ClickHouse/ClickBench

All issues in ClickHouse/ClickBench

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.