Remove obsolete unmanaged_memory_limit log warning after obmalloc removal

Open Beginner friendly
#1,269 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Tech stack
cpp
Domain
backend

Research direction

Inspect ob_server_config.cpp around line 207 and trace the check_limit warning described in the issue. Done means the obsolete unmanaged_memory_size warning is no longer emitted after obmalloc removal; verify the surrounding configuration logic still behaves as expected.

Written by the indexing model from the issue text.

Description

dima type: task

Description

After the removal of obmalloc, certain log warnings are no longer necessary.

Details

The following warning log is now obsolete and should be removed or suppressed:

[2026-08-07 16:12:18.275752] EDIAG [SHARE.CONFIG] check_limit (ob_server_config.cpp:207) [1652661][T1_TxLoopWorker_MemPrinter][Y0-0000000000000000-0-0] [lt=7][errcode=-4080] unmanaged_memory_size is over the limit(unmanaged_memory_size=2513899520, UNMANAGED_MEMORY_LIMIT=2147483648) BACKTRACE:0xa1be7...
Dominant language
C++
Stars
2.9k
Forks
342
Avg merge
2d 20h
Merged PRs (30d)
55

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.

More from oceanbase/seekdb

All issues in oceanbase/seekdb

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.