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

issue-1161: not initializing most of the per-filesystem request counters until we actually receive at least 1 request of the type #1711

Merged
merged 1 commit into from
Aug 3, 2024

Conversation

qkrorlqr
Copy link
Collaborator

@qkrorlqr qkrorlqr commented Aug 2, 2024

Unlike NBS we have a lot of different request types in Filestore. And we report a lot of metrics for each <requestType, fsId> pair which generates a lot of work for the monitoring systems that we use. Most of the filesystems never receive the majority of these request types. In this PR I'm not reporting any per-FS counters except Count and Errors/Fatal for the request types which have never been seen by this FS. It should radically decrease the total number of metrics that we report (we'll get rid of a lot of unnecessarily reported zeroes).

#1161

…ers until we actually receive at least 1 request of the type
Copy link
Contributor

github-actions bot commented Aug 2, 2024

Note

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

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

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

@qkrorlqr qkrorlqr merged commit 3c5b240 into main Aug 3, 2024
10 checks passed
@qkrorlqr qkrorlqr deleted the users/qkrorlqr/issue-1161-lazy-fs-counters-init branch August 3, 2024 11:08
qkrorlqr added a commit that referenced this pull request Aug 10, 2024
…ers until we actually receive at least 1 request of the type (#1711)
qkrorlqr added a commit that referenced this pull request Aug 11, 2024
…n local service; lazy filestore counters init; support for large unaligned writes in ThreeStageWrite mode (#1770)

* issue-1668: TLocalFileSystem::ReadDataAsync/WriteDataAsync  (#1686)

* issue-1668: preparing to make TLocalFileSystem::ReadData/ReadData async

* issue-1668: preparing to make TLocalFileSystem::ReadData/ReadData async - fix

* issue-1668: fixed LocalService double start, fixed missing xattr error code

* issue-1668: LocalService now uses TFileHandle instead of TFile; LocalService now uses libaio instead of synchronous pread/pwrite for ReadData/WriteData calls; added move assignment operator to TFileHandle

* issue-1668: fixed LocalService ut

* issue-1350: GetNodeAttrBatchEnabled: true for multitablet filestore tests (#1706)

* issue-1161: not generating deletion markers upon symlink removal (#1707)

* issue-1161: not initializing most of the per-filesystem request counters until we actually receive at least 1 request of the type (#1711)

* issue-1161: fixed stupid lazy counter init race (#1722)

* issue-1673: Unaligned requests support in ThreeStageWrite pipeline - IndexTablet part (#1740)

* issue-1673: UnalignedDataParts support in TIndexTabletActor::AddData, TODO: uts

* issue-1673: AddData now properly handles outdated UnalignedDataParts

* issue-1673: AddData + UnalignedDataParts ut

* issue-1673: AddData + UnalignedDataParts: using CommitId, generated in AddBlobTx (since the same CommitId is used for the blobs), adding some checks (#1754)

* issue-1673: AddData + UnalignedDataParts: using CommitId, generated in AddBlobTx (since the same CommitId is used for the blobs), adding some checks

* issue-1673: AddData + UnalignedDataParts: better error processing and logging, fixed ut

* issue-1673: supported ThreeStageWrites for large unaligned requests in StorageServiceActor (#1769)

* issue-1673: supported ThreeStageWrites for large unaligned requests in StorageServiceActor

* issue-1673: supported ThreeStageWrites for large unaligned requests in StorageServiceActor - fixed logging

* updated CMakeLists after merge
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.

3 participants