Fixed race conditions and bugs in xds client #941
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.
Summary
Fix three issues:
XdsClientImpl
currently fails to detect connection failure to the ADS server. Connection failure leads to no notification to theStreamObserver
sinceonError
andonCompleted
are terminal notifications. Instead, theonReady
notification needs to be relied on to detect successful connection establishment.startRpcStream
public method didn't use the single-threaded executor for execution. It also didn't check for an already existing stream, which could lead to multiple ads streams.Testing Done
Built local snapshot and deployed against
toki
. Typically it seems to take 1 sec for the stream to get ready. Tested against various scenarios:Normal state
Connection failure on startup (Observer pinned and crashed)
Start observer; immediately the stream becomes ready, and all the pending subscription requests are sent again
The local filestore is also updated immediately
Test Observer crash
Start Observer again after crash
Filestore is updated again