-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[enhance](mtmv)MTMV no longer generate cache when replaying logs #44283
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
run buildall |
morrySnow
approved these changes
Nov 19, 2024
github-actions
bot
added
the
approved
Indicates a PR has been approved by one committer.
label
Nov 19, 2024
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
TPC-H: Total hot run time: 45241 ms
|
ClickBench: Total hot run time: 31.84 s
|
run buildall |
TPC-H: Total hot run time: 44999 ms
|
ClickBench: Total hot run time: 32.1 s
|
starocean999
approved these changes
Nov 20, 2024
github-actions bot
pushed a commit
that referenced
this pull request
Nov 20, 2024
) ### What problem does this PR solve? When replaying logs, cache will no longer be generated because the catalog may not have been initialized or the dependent environment may not be connected, causing it to freeze here and preventing FE from starting The cost is that after the materialized view is refreshed, the cache of the follower node will be empty, and a cache will be generated when the query is first used Problem Summary: MTMV no longer generate cache when replaying logs
github-actions bot
pushed a commit
that referenced
this pull request
Nov 20, 2024
) ### What problem does this PR solve? When replaying logs, cache will no longer be generated because the catalog may not have been initialized or the dependent environment may not be connected, causing it to freeze here and preventing FE from starting The cost is that after the materialized view is refreshed, the cache of the follower node will be empty, and a cache will be generated when the query is first used Problem Summary: MTMV no longer generate cache when replaying logs
yiguolei
pushed a commit
that referenced
this pull request
Nov 25, 2024
…ng logs #44283 (#44308) Cherry-picked from #44283 Co-authored-by: zhangdong <[email protected]>
dataroaring
pushed a commit
that referenced
this pull request
Nov 26, 2024
…ng logs #44283 (#44307) Cherry-picked from #44283 Co-authored-by: zhangdong <[email protected]>
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
When replaying logs, cache will no longer be generated because the catalog may not have been initialized or the dependent environment may not be connected, causing it to freeze here and preventing FE from starting
The cost is that after the materialized view is refreshed, the cache of the follower node will be empty, and a cache will be generated when the query is first used
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
MTMV no longer generate cache when replaying logs
Release note
MTMV no longer generate cache when replaying logs
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)