-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Fix audit_storage issues #9265
Fix audit_storage issues #9265
Conversation
Result of foundationdb-pr-clang-ide on Linux CentOS 7
|
Doxense CI Report for Windows 10
|
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. A question. Let me try this out.
const UID id = UID::fromString(tokens[3].toString()); | ||
AuditStorageState res = wait(getAuditState(cx, type, id)); | ||
printf("Audit result is:\n%s", res.toString().c_str()); | ||
} else if (tokencmp(tokens[2], "recent")) { | ||
const int count = std::stoi(tokens[3].toString()); | ||
int count = 5; |
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.
What is this? 5 'rows'? We should add this to the help output, that 5 is the default 'Count' (I can do that over in #9266).
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.
I think default should be ROW_LIMIT_UNLIMITED -- I think that would make more sense to the user. What do you think ?
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.
That's a good point, I put CLIENT_KNOBS->TOO_MANY
as the default.
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.
Is TOO_MANY too small? Its only 1M? Thanks.
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.
My current plan is to keep only the most recent N
audit records per audit type, I feel N
would be smaller than 1M, and a background process will be added to GC the earlier audit results.
What will the user experience be? When the audit completes, its id is cleaned. If user queries for the state of their audit, what will they get? Thanks. |
Result of foundationdb-pr on Linux CentOS 7
|
Result of foundationdb-pr-clang on Linux CentOS 7
|
Result of foundationdb-pr-cluster-tests on Linux CentOS 7
|
get_audit_status.
At this moment, all the audit results are kept forever, in the future, I will add a background GC process to keep only the recent |
Doxense CI Report for Windows 10
|
Result of foundationdb-pr-clang-ide on Linux CentOS 7
|
Result of foundationdb-pr-macos-m1 on macOS Monterey 12.x
|
Result of foundationdb-pr-macos on macOS Monterey 12.x
|
Result of foundationdb-pr on Linux CentOS 7
|
Result of foundationdb-pr-clang on Linux CentOS 7
|
Result of foundationdb-pr-cluster-tests on Linux CentOS 7
|
Talked offline w/ @liquid-helium . +1 on this PR. Cleanup and 'count' to be addressed in follow-ons. |
* main: (22 commits) move feed cleanup check to after data is guaranteed to be available for granule (apple#9283) remove test timeout Reduce logging level for verbose events Added documentation for consistencyscan CLI command. Fix audit_storage issues (apple#9265) Update bindings/bindingtester/spec/tenantTester.md Update bindings/bindingtester/spec/tenantTester.md update bindingtester spec Fixing SkewedReadWrite to load its metadata in a transactionally consistent way (apple#9274) push string onto stack when active tenant is set Add comments on why custom encoding is needed patch to fix some existing bindingtester issues add arg and return type to the c_api for impl.py Fix includes Add from_7.0.0_until_7.2.0 for UpgradeAndBackupRestore tests Change UpgradeAndBackupRestore to from_7.2.4 Add a new toml option to disable failure injection workload Change SubmitBackup to only reboot in Attrition add method to return idfuture add to java and python stack tester ...
* main: (23 commits) Handle EKP Tenant Not Found Errors (apple#9261) move feed cleanup check to after data is guaranteed to be available for granule (apple#9283) remove test timeout Reduce logging level for verbose events Added documentation for consistencyscan CLI command. Fix audit_storage issues (apple#9265) Update bindings/bindingtester/spec/tenantTester.md Update bindings/bindingtester/spec/tenantTester.md update bindingtester spec Fixing SkewedReadWrite to load its metadata in a transactionally consistent way (apple#9274) push string onto stack when active tenant is set Add comments on why custom encoding is needed patch to fix some existing bindingtester issues add arg and return type to the c_api for impl.py Fix includes Add from_7.0.0_until_7.2.0 for UpgradeAndBackupRestore tests Change UpgradeAndBackupRestore to from_7.2.4 Add a new toml option to disable failure injection workload Change SubmitBackup to only reboot in Attrition add method to return idfuture ...
Some quick fixes, the complete fix is in #9264
Code-Reviewer Section
The general pull request guidelines can be found here.
Please check each of the following things and check all boxes before accepting a PR.
For Release-Branches
If this PR is made against a release-branch, please also check the following:
release-branch
ormain
if this is the youngest branch)