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, merge to stable]: issue-1795: LargeDeletionMarkers, issue-1922: making background ops' read/writeblob requests async, issue-1922: avoiding Compaction loops, allow for some actions to ignore auth, add information about backpressure to the monpage, issue-1146: add setters for in-memory state #2020

Closed

Conversation

debnatkh
Copy link
Collaborator

debnatkh and others added 8 commits September 13, 2024 00:56
allow for some actions to ignore auth
…r tables (#1961)

* issue-1146: add setters for in-memory state, temporary get rid of _Ver tables
* issue-1795: LargeDeletionMarkers WIP

* issue-1795: 1. making MaxFileBlocks configurable via StorageServiceConfig; 2. added a bunch of parameters which will control the way LargeDeletionMarkers work; 3. loading LargeDeletionMarkers upon tablet startup

* issue-1795: writing LargeDeletionMarkers instead of normal DeletionMarkers if the deleted range is big enough and the corresponding StorageServiceConfig params are set

* issue-1795: LargeDeletionMarkers data structure implementation + simple ut

* issue-1795: LargeDeletionMarkers data structure implementation + simple ut - fix

* issue-1795: LargeDeletionMarkers data structure implementation + simple ut - cleanup NodeId2Markers

* issue-1795: extracted TSparseSegment from TLargeBlocks and added uts for it

* issue-1795: implemented Cleanup for LargeDeletionMarkers

* issue-1795: fixed Cleanup for LargeDeletionMarkers, added large file truncation ut

* issue-1795: fixed Cleanup for LargeDeletionMarkers, added large file truncation ut - more ut fixes

* issue-1795: actually applying LargeDeletionMarkers to the blobs not affected by regular DeletionMarkers upon Cleanup

* issue-1795: fixed test - now UnlinkNode triggers FlushBytes op so the test is incorrect, to fix it we need to increase FlushBytesThreshold which actually requires making it ui64 instead of ui32

* issue-1795: LargeDeletionMarkers - added more docs, fixed some minor review issues

* issue-1795: LargeDeletionMarkers - added more uts, fixed some bugs; changed MaxFileBlocks type from uint64 to uint32 in StorageServiceConfig to signal that values greater than 2^31 shouldn't be used without prior testing and logic review

* issue-1795: fixed linking
…t made in AddBlob for Compaction requests by CompactionThreshold - 1 (#2011)

* issue-1922: avoiding Compaction loops by limiting BlobsCount increment made in AddBlob for Compaction requests by CompactionThreshold - 1

* issue-1922: restoring stats.BlobsCount = 0 logic upon AddBlob_Compaction

* issue-1922: simplified AddBlob_Compaction
Copy link
Contributor

Note

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

🟢 default-linux-x86-64-relwithdebinfo: all tests PASSED for commit bfebb2f.

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

@debnatkh debnatkh changed the title Users/debnatkh/merge to stable 23 3 7061 [Filestore, merge to stable]: issue-1795: LargeDeletionMarkers, issue-1922: making background ops' read/writeblob requests async, issue-1922: avoiding Compaction loops, allow for some actions to ignore auth, add information about backpressure to the monpage, issue-1146: add setters for in-memory state Sep 13, 2024
@debnatkh debnatkh marked this pull request as ready for review September 13, 2024 10:32
@debnatkh debnatkh closed this Sep 13, 2024
@debnatkh debnatkh deleted the users/debnatkh/merge-to-stable-23-3-7061 branch September 24, 2024 09:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants