-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[bug](GC)the issue of incorrect disk usage #18397
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
|
clang-tidy review says "All clean, LGTM! 👍" |
|
run all |
|
run p0 |
1 similar comment
|
run p0 |
|
run beut |
|
run feut |
|
run p0 |
|
ru beut |
|
run clickbench |
|
TeamCity pipeline, clickbench performance test result: |
|
clang-tidy review says "All clean, LGTM! 👍" |
3 similar comments
|
clang-tidy review says "All clean, LGTM! 👍" |
|
clang-tidy review says "All clean, LGTM! 👍" |
|
clang-tidy review says "All clean, LGTM! 👍" |
|
run buildall |
morningman
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
…#18485) 1. If we set hadoop user property along with kerberos info, the authentication will fail. 2. fix some minor issue of local fs, follow up apache#18397 3. Add KW_HOSTNAME to keywords region, follow up apache#17329 4. Fix tvf not working with pipeline engine, follow up apache#18376
…#18485) 1. If we set hadoop user property along with kerberos info, the authentication will fail. 2. fix some minor issue of local fs, follow up apache#18397 3. Add KW_HOSTNAME to keywords region, follow up apache#17329 4. Fix tvf not working with pipeline engine, follow up apache#18376
Proposed changes
disk used capacity is incorrect:

DataUsedCapacity+AvailCapacity !=TotalCapacity
Problem summary
some invalid rowset rowset not be deleted for ever due to the bug:

when key_may_exists() return true not means it is real exists
Checklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...