-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Enhancement] Make some system tables query from leader fe (backport #51763) #51823
Conversation
Signed-off-by: wyb <[email protected]> (cherry picked from commit da80492) # Conflicts: # fe/fe-core/src/main/java/com/starrocks/catalog/system/SystemTable.java # fe/fe-core/src/main/java/com/starrocks/catalog/system/information/BeDataCacheMetricsTable.java # fe/fe-core/src/main/java/com/starrocks/catalog/system/information/TaskRunsSystemTable.java # fe/fe-core/src/main/java/com/starrocks/catalog/system/information/TasksSystemTable.java # fe/fe-core/src/main/java/com/starrocks/catalog/system/information/TemporaryTablesTable.java # fe/fe-core/src/main/java/com/starrocks/sql/plan/PlanFragmentBuilder.java
Cherry-pick of da80492 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
@mergify[bot]: Backport conflict, please reslove the conflict and resubmit the pr |
Quality Gate passedIssues Measures |
Why I'm doing:
some metadata may be inaccurate in the follower fe, because they may be not persisted in leader fe,
such as routine load job state changed from NEED_SCHEDULE to RUNNING.
What I'm doing:
these system tables should query from leader fe.
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check:
This is an automatic backport of pull request #51763 done by [Mergify](https://mergify.com). ## Why I'm doing: some metadata may be inaccurate in the follower fe, because they may be not persisted in leader fe, such as routine load job state changed from NEED_SCHEDULE to RUNNING.
What I'm doing:
these system tables should query from leader fe.
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist: