Fix persistent search restart with affinity-based load balancing (backport) - #333
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR is auto-generated as a backport of #332.
Original title: Fix persistent search restart with affinity-based load balancing
Original author: fyrbach
Problem
When using affinity-based request load balancing, persistent search was not restarted after an underlying LDAP connection error.
Cause
The affinity request load balancer provides proxy connections and obtains a real connection for each individual
request. As a result, the connection event listener added in #269 was never notified of underlying connection errors.
Fix
Trigger the restart from the asynchronous search failure handler rather than a connection event listener.
How to verify
Use affinity-based load balancing, terminate the underlying LDAP connection, and verify that persistent search is
restarted.