-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: show flow's mem usage in INFORMATION_SCHEMA.FLOWS #4890
base: main
Are you sure you want to change the base?
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
ff13cb1
to
1b8aeec
Compare
39fda57
to
1b0b0ef
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4890 +/- ##
==========================================
- Coverage 84.19% 83.81% -0.39%
==========================================
Files 1137 1139 +2
Lines 209796 210217 +421
==========================================
- Hits 176646 176198 -448
- Misses 33150 34019 +869 |
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
Add a column to show flow's mem usage in system table, so one can tune flow's ttl option as needed.
Please explain IN DETAIL what the changes are in this PR and why they are needed:
in distributed mode Flownode's heartbeat task will reguarly ask for a
StateReport
which include all flows' mem usage data, and send them to metasrv, then metasrv can use this info to build system table, however there is a small latency in data update since heartbeat duration is in seconds but this usually is ok since flow's mem usage grow very slowly usually. In standalone mode can just query flow's mem sizeChecklist