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

fix(connection): Fix pipelined command counter #2201

Merged
merged 3 commits into from
Nov 23, 2023

Conversation

dranikpg
Copy link
Contributor

  • Pipelined command counter is increased even if SendAsync ignores it afterwards
  • Add break after yield in connection close
  • Add more debug info on check fail

Signed-off-by: Vladislav Oleshko <vlad@dragonflydb.io>
bool threshold_reached = dispatch_q_cmds_count_ > squashing_threshold;
bool are_all_plain_cmds = dispatch_q_cmds_count_ == dispatch_q_.size();
bool threshold_reached = pending_pipeline_cmd_cnt_ > squashing_threshold;
bool are_all_plain_cmds = pending_pipeline_cmd_cnt_ == dispatch_q_.size();
Copy link
Collaborator

Choose a reason for hiding this comment

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

what are monitor messages? are they PipelineMsg?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, they have their own type MonitorMessage. Btw pending_pipeline_cmd_cnt_ was Romans suggestion 😆 I also think it's okay given it has a comment

@dranikpg dranikpg merged commit 9686f69 into dragonflydb:main Nov 23, 2023
7 checks passed
@dranikpg dranikpg deleted the fix-squashing-2 branch November 23, 2023 16:01
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.

None yet

3 participants