feat(sdk): configure connection timeout and banning #1629
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue being fixed or feature implemented
With a high request rate we need to increase timeouts. In some cases, we would like to wait for responses when all STs are broadcast
What was done?
connect_timeout
to DAPI Client settingsban_failed_address
to DAPI Client settingswait_for_response
forPutDocument
traitHow Has This Been Tested?
Running locally in rs platform explorer
Breaking Changes
None
Checklist:
For repository code-owners and collaborators only