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

Better fsync tracking. #13204

Closed
yugabyte-ci opened this issue Jul 7, 2022 · 1 comment
Closed

Better fsync tracking. #13204

yugabyte-ci opened this issue Jul 7, 2022 · 1 comment
Labels
area/docdb YugabyteDB core features jira-originated kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue

Comments

@yugabyte-ci
Copy link
Contributor

yugabyte-ci commented Jul 7, 2022

Jira Link: DB-2876

I see the following log 400k/h on one cluster.

Time spent Fsync log took a long time: real 0.072s user 0.000s sys 0.000s

This seems recessive. Maybe we can cap this log to at most once per second?

A better way to track this would be a distribution metric for fsync latency. This would give us better visibility and greatly reduce the cost of tracking that data.

@yugabyte-ci yugabyte-ci added jira-originated kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue status/awaiting-triage Issue awaiting triage labels Jul 7, 2022
@bmatican
Copy link
Contributor

Reducing log frequency tracked in #13203

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docdb YugabyteDB core features jira-originated kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue
Projects
None yet
Development

No branches or pull requests

5 participants