-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[improve](load) improve error message in commit #48316
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
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
TPC-H: Total hot run time: 31816 ms |
TPC-DS: Total hot run time: 184058 ms |
ClickBench: Total hot run time: 30.8 s |
liaoxin01
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
dataroaring
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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.
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.
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.
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.
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.
What problem does this PR solve?
Issue Number: DORIS-17659 DORIS-18383
Problem Summary:
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.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)