Skip to content

branch-2.1: [improve](load) improve error message in commit #48316 #48891

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
Merged
yiguolei merged 1 commit into from
Mar 11, 2025
Merged

branch-2.1: [improve](load) improve error message in commit #48316 #48891

yiguolei merged 1 commit into from
Mar 11, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Mar 11, 2025

Cherry-picked from #48316

@kaijchen
[improve](load) improve error message in commit (#48316)
ee1d100 
In a 3-replica setup, when the BE detects a write error on one replica,
it continues submitting the commit information. If the FE checks the
commit status and finds that one of the two successful replicas is
missing the previous version, an error is returned. However, since the
BE does not report the failure reason, the FE's error message does not
provide details on the underlying cause.

This PR improves the error message for this scenario. It advises users
to check the BE logs and SHOW TABLET for more detailed error reasons and
suggests retrying the operation later.
@github-actions github-actions bot requested a review from yiguolei as a code owner March 11, 2025 01:34
@Thearas
Copy link
Contributor

Thearas commented Mar 11, 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 Mar 11, 2025
@Thearas
Copy link
Contributor

Thearas commented Mar 11, 2025

run buildall

@yiguolei yiguolei merged commit 90f7f64 into branch-2.1 Mar 11, 2025
20 checks passed
@github-actions github-actions bot deleted the auto-pick-48316-branch-2.1 branch March 11, 2025 08:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguolei yiguolei yiguolei approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@Thearas @yiguolei @dataroaring @kaijchen