Skip to content
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

[fix](regression)Fix unstable compaction related cases #46920

Merged
merged 3 commits into from
Jan 15, 2025

Conversation

qidaye
Copy link
Contributor

@qidaye qidaye commented Jan 13, 2025

What problem does this PR solve?

Related PR: #45761

Problem Summary:

  1. Added wait_for_build_index_on_partition_finish calls to ensure indexes are built before triggering compaction.

  2. When we do index compaction fault injection test, compaction status e-6010 is expected sometimes. Added an ignored_errors parameter to the trigger_and_wait_compaction method, allowing specific errors to be ignored during compaction.

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@hello-stephen
Copy link
Contributor

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?

@qidaye
Copy link
Contributor Author

qidaye commented Jan 13, 2025

run buildall

Copy link
Contributor

@zzzxl1993 zzzxl1993 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

PR approved by anyone and no changes requested.

airborne12
airborne12 previously approved these changes Jan 14, 2025
Copy link
Member

@airborne12 airborne12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Jan 14, 2025
Copy link
Contributor

PR approved by at least one committer and no changes requested.

@qidaye qidaye marked this pull request as draft January 14, 2025 07:38
@qidaye qidaye marked this pull request as ready for review January 14, 2025 08:01
@github-actions github-actions bot removed the approved Indicates a PR has been approved by one committer. label Jan 14, 2025
@qidaye
Copy link
Contributor Author

qidaye commented Jan 14, 2025

run buildall

Copy link
Contributor

@py023 py023 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rest LGTM

@qidaye
Copy link
Contributor Author

qidaye commented Jan 14, 2025

run buildall

Copy link
Contributor

@py023 py023 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Collaborator

@shuke987 shuke987 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@airborne12 airborne12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

PR approved by at least one committer and no changes requested.

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Jan 15, 2025
@qidaye qidaye merged commit c76f309 into apache:master Jan 15, 2025
31 checks passed
@qidaye qidaye deleted the fix_case_trigger_with_retry branch January 15, 2025 02:18
qidaye added a commit to qidaye/incubator-doris that referenced this pull request Jan 15, 2025
Related PR: apache#45761

Problem Summary:

1. Added `wait_for_build_index_on_partition_finish` calls to ensure
indexes are built before triggering compaction.

2. When we do index compaction fault injection test, compaction status
`e-6010` is expected sometimes. Added an `ignored_errors` parameter to
the `trigger_and_wait_compaction` method, allowing specific errors to be
ignored during compaction.
qidaye added a commit to qidaye/incubator-doris that referenced this pull request Jan 15, 2025
Related PR: apache#45761

Problem Summary:

1. Added `wait_for_build_index_on_partition_finish` calls to ensure
indexes are built before triggering compaction.

2. When we do index compaction fault injection test, compaction status
`e-6010` is expected sometimes. Added an `ignored_errors` parameter to
the `trigger_and_wait_compaction` method, allowing specific errors to be
ignored during compaction.
qidaye added a commit to qidaye/incubator-doris that referenced this pull request Jan 15, 2025
Related PR: apache#45761

Problem Summary:

1. Added `wait_for_build_index_on_partition_finish` calls to ensure
indexes are built before triggering compaction.

2. When we do index compaction fault injection test, compaction status
`e-6010` is expected sometimes. Added an `ignored_errors` parameter to
the `trigger_and_wait_compaction` method, allowing specific errors to be
ignored during compaction.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by one committer. dev/2.1.8-merged dev/3.0.4-merged reviewed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants