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 no_response_threshold(120s) for No response requests #376

Merged
merged 5 commits into from
Dec 1, 2022

Conversation

hocktea214
Copy link
Collaborator

@hocktea214 hocktea214 commented Nov 29, 2022

Signed-off-by: huxiangyuan [email protected]

Description

There're two checks for no response request and completed request with same 15s check.
In fact, complete request should check timely with 15s
But the no response request should wait long period with 120s which is set with no_response_threshold in config file.

Besides, there may be multi-send with same request, use atomic check for send once.

Related Issue

Motivation and Context

How Has This Been Tested?

@hocktea214 hocktea214 requested a review from dxsup November 29, 2022 11:15
@hocktea214 hocktea214 force-pushed the add-noresponse-threshol branch from 4a10d02 to 75d1696 Compare December 1, 2022 03:05
@hocktea214 hocktea214 changed the title Add no_response_threshold(30s) for No response requests Add no_response_threshold(120s) for No response requests Dec 1, 2022
@hocktea214 hocktea214 force-pushed the add-noresponse-threshol branch from bcd17fc to a34aaee Compare December 1, 2022 11:40
@dxsup dxsup merged commit 8164aea into KindlingProject:main Dec 1, 2022
@hocktea214 hocktea214 deleted the add-noresponse-threshol branch December 22, 2022 01:16
NeJan2020 pushed a commit to NeJan2020/kindling that referenced this pull request May 4, 2023
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.

2 participants