Skip to content

[test](docker) Verify DML and 3-replica create table when one BE is down#63401

Open
deardeng wants to merge 1 commit into
apache:masterfrom
deardeng:add-ddl-case
Open

[test](docker) Verify DML and 3-replica create table when one BE is down#63401
deardeng wants to merge 1 commit into
apache:masterfrom
deardeng:add-ddl-case

Conversation

@deardeng
Copy link
Copy Markdown
Collaborator

Add a non-cloud docker regression case that brings up 1 FE + 4 BE, stops one BE, and then verifies on the remaining 3 BEs:

  1. truncate / delete / update on an existing 3-replica MOW unique-key table (now with 2 replicas alive per tablet) still succeed.
  2. Creating a new 3-replica table still succeeds and the replicas are distributed across the 3 alive BEs.

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

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

Add a non-cloud docker regression case that brings up 1 FE + 4 BE,
stops one BE, and then verifies on the remaining 3 BEs:

  1. truncate / delete / update on an existing 3-replica MOW unique-key
     table (now with 2 replicas alive per tablet) still succeed.
  2. Creating a new 3-replica table still succeeds and the replicas are
     distributed across the 3 alive BEs.
@hello-stephen
Copy link
Copy Markdown
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?

@deardeng
Copy link
Copy Markdown
Collaborator Author

run buildall

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants