bugfix: respect max retry after using balancer pool #2331
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.
In the balancer phase, when obtaining a connection from the upstream connection pool, the
cached
attribute of the peer connection is set to 1(pc->cached = 1;
), indicating that the connection is obtained from the cache.If an error occurs during the use of this connection, such as "upstream prematurely closed connection" the system will increase the
tries
attribute of the peer connection by executingu->peer.tries++
.This PR restores tries by callbacks to the balancer when
u->peer.tries++
is unexpectedly set.I hereby granted the copyright of the changes in this pull request
to the authors of this lua-nginx-module project.