4paradigm / 4paradigm/OpenMLDB
show table status will get the incorrect memory usage for mulltiple replicas
Open
bug
documentation
- Dominant language
- C++
- Stars
- 1.7k
- Forks
- 331
- Avg merge
- 12d 12h
- Merged PRs (30d)
- 1
Description
Now we use "show table status" and get the incorrect memory usage.
Contributor guide
Research direction
The issue mentions 'show table status' returning incorrect memory usage for multiple replicas. Look for SQL command handling and memory usage tracking in the codebase, likely in the SQL execution or replication modules. Check existing tests for 'show table status' to understand the expected behavior. The fix will involve updating the memory calculation logic to account for replicas correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100