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

add commit/apply duration for raft store #13946

Merged
merged 5 commits into from Dec 30, 2022

Conversation

bufferflies
Copy link
Contributor

@bufferflies bufferflies commented Dec 15, 2022

Signed-off-by: bufferflies 1045931706@qq.com

What is changed and how it works?

Issue Number: Ref #12842

What's Changed:

Related changes

Check List

Tests

  • Manual test (add detailed scripts or steps below)
    Apply duration

image

Apply wait duration
image

Side effects

Release note

None.

Signed-off-by: bufferflies <1045931706@qq.com>
@ti-chi-bot
Copy link
Member

ti-chi-bot commented Dec 15, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • BusyJay
  • tonyxuqqi

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@bufferflies
Copy link
Contributor Author

/cc @tonyxuqqi @SpadeA-Tang

@ti-chi-bot
Copy link
Member

@bufferflies: GitHub didn't allow me to request PR reviews from the following users: SpadeA-Tang.

Note that only tikv members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @tonyxuqqi @SpadeA-Tang

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@bufferflies
Copy link
Contributor Author

/cc @SpadeA-Tang

@ti-chi-bot
Copy link
Member

@bufferflies: GitHub didn't allow me to request PR reviews from the following users: SpadeA-Tang.

Note that only tikv members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @SpadeA-Tang

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Signed-off-by: bufferflies <1045931706@qq.com>
@@ -126,6 +128,7 @@ impl<EK: KvEngine, R: ApplyResReporter> ApplyFsm<EK, R> {
}
}
self.apply.flush();
STORE_APPLY_LOG_HISTOGRAM.observe(duration_to_sec(received_time.saturating_elapsed()));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not accurate as the fsm may be reschedule where there is an await.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From end-to-end perspective, I think it's the time the user request actually pays for the apply. So it's ok.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it's not. It just the time apply finish a round of processing. Before the timer stops, user may have sent and received multiple round of req/resp.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it, I will using water fall to replace removing this metrics in next pr.

Copy link
Member

@BusyJay BusyJay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rest LGTM

@ti-chi-bot ti-chi-bot added the status/LGT1 Status: PR - There is already 1 approval label Dec 28, 2022
@ti-chi-bot ti-chi-bot added status/LGT2 Status: PR - There are already 2 approvals and removed status/LGT1 Status: PR - There is already 1 approval labels Dec 29, 2022
Signed-off-by: bufferflies <1045931706@qq.com>
Signed-off-by: bufferflies <1045931706@qq.com>
Signed-off-by: bufferflies <1045931706@qq.com>
@iosmanthus
Copy link
Member

/merge

@ti-chi-bot
Copy link
Member

@iosmanthus: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: 8d6c5f7

@ti-chi-bot ti-chi-bot added the status/can-merge Status: Can merge to base branch label Dec 30, 2022
@ti-chi-bot ti-chi-bot merged commit 64293cb into tikv:master Dec 30, 2022
@ti-chi-bot ti-chi-bot added this to the Pool milestone Dec 30, 2022
@bufferflies bufferflies deleted the raft_store_metrics branch December 30, 2022 09:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note-none size/S status/can-merge Status: Can merge to base branch status/LGT2 Status: PR - There are already 2 approvals
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants