Skip to content

branch-3.0: [Feature](Compaction)Improve Compaction Profiling and Logging #50950 #51071

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.

Sign up for GitHub

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

Jump to bottom
Closed
github-actions wants to merge 1 commit into from
Closed

branch-3.0: [Feature](Compaction)Improve Compaction Profiling and Logging #50950 #51071

github-actions wants to merge 1 commit into from

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented May 20, 2025

Cherry-picked from #50950

@Yukang-Lian @Yoruet
[Feature](Compaction)Improve Compaction Profiling and Logging (#50950)
aa3df8e 
### What problem does this PR solve?

Issue Number: close #xxx

Related PR: #42227

Problem Summary:

Issue Number: close #41753
Add detailed parameters to compaction status:

add

last cumulative failure time
last base failure time
last full failure time
last cumulative success time
last base success time
last full success time
last cumulative schedule time
last base schedule time
last full schedule time
last cumulative status
last base status
last full status
in cloud_tablet.cpp

and add

last cumulative schedule time
last full schedule time
last cumulative status
last full status
in tablet.cpp

Co-authored-by: yoruet <1559650411@qq.com>
@github-actions github-actions bot requested a review from dataroaring as a code owner May 20, 2025 07:15
@hello-stephen
Copy link
Contributor

hello-stephen commented May 20, 2025

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaring dataroaring reopened this May 20, 2025
@hello-stephen
Copy link
Contributor

hello-stephen commented May 20, 2025

run buildall

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dataroaring dataroaring Awaiting requested review from dataroaring

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@hello-stephen @dataroaring @Yukang-Lian