Skip to content
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

[Filestore] issue-652: use currentCommitId-1 instead of currentCommitId for CollectGarbage #1135

Merged
merged 7 commits into from
May 15, 2024

Conversation

debnatkh
Copy link
Collaborator

@debnatkh debnatkh commented May 6, 2024

References #652

Cleanup operation acquires a collect barrier with the current commitId to protect the data with the current commitId (or greater) from being tampered with.

Thus, it will be more logical to modify the CollectGarbage operation not to use the currentCommitId, but use currentCommitId - 1, if no barriers are present.

@debnatkh debnatkh added the filestore Add this label to run only cloud/filestore build and tests on PR label May 6, 2024
Copy link
Contributor

github-actions bot commented May 6, 2024

Note

This is an automated comment that will be appended during run.

🟢 linux-x86_64-relwithdebinfo: all tests PASSED for commit bcf5a90.

TESTS PASSED ERRORS FAILED SKIPPED MUTED?
1539 1539 0 0 0 0

@debnatkh debnatkh changed the title issue-652: use currentCommitId-1 [Filestore] issue-652: use currentCommitId-1 instead of currentCommitId for CollectGarbage May 6, 2024
@debnatkh debnatkh force-pushed the users/debnatkh/issue-652-2 branch from ca1c5ab to ed6336e Compare May 7, 2024 15:01
@debnatkh
Copy link
Collaborator Author

debnatkh commented May 7, 2024

Some tests use CollectGarbage and expect all garbage blobs to be collected (including ones with currentCommitid. A new private event that propagates currentCommitid is introduced to meet these expectations.

Copy link
Contributor

github-actions bot commented May 7, 2024

Note

This is an automated comment that will be appended during run.

🟢 linux-x86_64-relwithdebinfo: all tests PASSED for commit ed6336e.

TESTS PASSED ERRORS FAILED SKIPPED MUTED?
1541 1541 0 0 0 0

Copy link
Contributor

github-actions bot commented May 8, 2024

Note

This is an automated comment that will be appended during run.

🔴 linux-x86_64-relwithdebinfo: some tests FAILED for commit de5ae2c.

TESTS PASSED ERRORS FAILED SKIPPED MUTED?
1268 1267 0 1 0 0

@debnatkh debnatkh force-pushed the users/debnatkh/issue-652-2 branch from de5ae2c to 09d8896 Compare May 8, 2024 19:22
Copy link
Contributor

github-actions bot commented May 8, 2024

Note

This is an automated comment that will be appended during run.

🟢 linux-x86_64-relwithdebinfo: all tests PASSED for commit 09d8896.

TESTS PASSED ERRORS FAILED SKIPPED MUTED?
1541 1541 0 0 0 0

qkrorlqr
qkrorlqr previously approved these changes May 9, 2024
qkrorlqr
qkrorlqr previously approved these changes May 10, 2024
Copy link
Contributor

Note

This is an automated comment that will be appended during run.

🔴 linux-x86_64-relwithdebinfo: some tests FAILED for commit 233f239.

TESTS PASSED ERRORS FAILED SKIPPED MUTED?
1268 1267 0 1 0 0

Copy link
Contributor

Note

This is an automated comment that will be appended during run.

🟢 linux-x86_64-relwithdebinfo: all tests PASSED for commit 8761cf1.

TESTS PASSED ERRORS FAILED SKIPPED MUTED?
1543 1543 0 0 0 0

@debnatkh debnatkh force-pushed the users/debnatkh/issue-652-2 branch from 88cec4a to 0c551e6 Compare May 14, 2024 12:02
@debnatkh debnatkh force-pushed the users/debnatkh/issue-652-2 branch from 0c551e6 to 5d81c2a Compare May 14, 2024 13:04
Copy link
Contributor

Note

This is an automated comment that will be appended during run.

🔴 linux-x86_64-relwithdebinfo: some tests FAILED for commit 5d81c2a.

TESTS PASSED ERRORS FAILED SKIPPED MUTED?
1317 1245 0 72 0 0

Copy link
Contributor

Note

This is an automated comment that will be appended during run.

🟢 linux-x86_64-relwithdebinfo: all tests PASSED for commit 311c507.

TESTS PASSED ERRORS FAILED SKIPPED MUTED?
1545 1545 0 0 0 0

@debnatkh debnatkh merged commit b8dc78c into main May 15, 2024
9 checks passed
@debnatkh debnatkh deleted the users/debnatkh/issue-652-2 branch May 15, 2024 18:06
debnatkh added a commit that referenced this pull request May 24, 2024
…mitId` for `CollectGarbage` (#1135)

issue-652: use currentCommitId-1
debnatkh added a commit that referenced this pull request May 27, 2024
…duce getnodeattr cache (#1272)

* [Filestore] issue-652: use `currentCommitId-1` instead of `currentCommitId` for `CollectGarbage` (#1135)

issue-652: use currentCommitId-1

* issue-1146: cache `GetNodeAttr` results (#1218)

* issue-1146: cache getnodeattr results

* fix cmake build for b8dc78c

* fix cmake build for 27e48d2

* trigger restart
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
filestore Add this label to run only cloud/filestore build and tests on PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants