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

ability to overwrite default response counter limit (10) #278

Merged
merged 2 commits into from
Jun 8, 2021
Merged

ability to overwrite default response counter limit (10) #278

merged 2 commits into from
Jun 8, 2021

Conversation

wareczek
Copy link
Contributor

@wareczek wareczek commented Jun 7, 2021

Description

Library returns error "zookeeper_process returned no response too many times: 11".
We wanted to add a flag using which will be possible to overwrite the default response counter limit (10).

Motivation and Context

We have nodes in ZK with a lot of data and the server responds after a couple more tries than 10, about ~40.

How Has This Been Tested?

Changed value of a new flag "response_counter_limit" to "100" and data was received.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

@DavidVujic
Copy link
Collaborator

Very nice @wareczek, thank you for this PR!

I'll have a look as soon as possible.

@DavidVujic DavidVujic self-requested a review June 7, 2021 19:16
@DavidVujic DavidVujic merged commit 06d2580 into yfinkelstein:master Jun 8, 2021
@wareczek
Copy link
Contributor Author

wareczek commented Jun 8, 2021

@DavidVujic thanks for merge! When could you release this to npm? :)

@wareczek wareczek deleted the feature/response_counter_limit branch June 8, 2021 22:31
@DavidVujic
Copy link
Collaborator

@wareczek v4.10.0 is out! 😄

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.

4 participants