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.

Sign up for GitHub

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

Jump to bottom

startup error ：void shard_connection::push_req(request*):Assertion 'm_request_per_cur_interval > 0 ' failed #283

Open
Supergirlzjl opened this issue Dec 28, 2024 · 0 comments
Open

startup error ：void shard_connection::push_req(request*):Assertion 'm_request_per_cur_interval > 0 ' failed #283

Supergirlzjl opened this issue Dec 28, 2024 · 0 comments

Comments

@Supergirlzjl
Copy link

Supergirlzjl commented Dec 28, 2024 •
edited
Loading

When we use the --rate-limiting parameter in the 2.1.2 version of memtier_benchmark, the following error is occasionally reported when starting. I don't know if it is related to the size setting of the parameter value. Are there any requirements for the size of this parameter?

benchmark-error
@Supergirlzjl Supergirlzjl changed the title When using the --rate-limiting parameter in memtier_benchmark version 2.1.2, the startup error void shard_connection::push_req(request*):Assertion 'm_request_per_cur_interval > 0 ' failed startup error ：void shard_connection::push_req(request*):Assertion 'm_request_per_cur_interval > 0 ' failed Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Supergirlzjl