Repository navigation
xDS: fix DistributorWatcher thread safety in CertificateProvider (v1.85.x backport) - #13133
Merged
kannanjgithub merged 1 commit intoOct 19, 2026
Conversation
…c#13087) A gRPC client using xDS-driven mTLS does two things concurrently: 1. Certificate provider: watches cert files on disk, periodically reloads them, and notifies subscribers when certs change. 2. Channel subscriptions: each gRPC channel that needs mTLS registers a watcher on the cert provider to get the TLS credentials. The `DistributorWatcher` sits in the middle and fans out: one cert provider pushes updates to it, and it distributes to N channel watchers. I think there are two conditions in this that can lead to a `ConcurrentModificationException`: 1. `updateSpiffeTrustMap` isn't synchronized (unlike `updateCertificate` and `updateTrustedRoots`), so it can race against `addWatcher`/`removeWatcher` from another thread. 2. if callbacks mutate their own subscription. A callchain (line numbers per 1.83.0 / 1084e97) for that is: ``` DistributorWatcher.onError() CertificateProvider.java:126 → for (watcher : downstreamWatchers) CertificateProvider.java:127 → watcher.onError(errorStatus) CertificateProvider.java:128 → DynamicSslContextProvider.onError() DynamicSslContextProvider.java:143 → callback.onException(error) DynamicSslContextProvider.java:145 → SslContextProviderSupplier.onException() SslContextProviderSupplier.java:79 → releaseSslContextProvider(toRelease) SslContextProviderSupplier.java:81 → TlsContextManagerImpl.releaseClient...() TlsContextManagerImpl.java:78 → ReferenceCountingMap.releaseInternal() ReferenceCountingMap.java:89 → if refcount == 0: value.close() ReferenceCountingMap.java:95 → CertProviderSslContextProvider.close() CertProviderSslContextProvider.java:216 → certHandle.close() CertProviderSslContextProvider.java:218 → Handle.close() CertificateProviderStore.java:62 → distWatcher.removeWatcher() CertificateProviderStore.java:64 <-- REENTRANT ``` We observed `ConcurrentModificationException` in `updateSpiffeTrustMap()` in production, consistent with the unsynchronized iteration described above. We also observed startup RPC deadlines during the rollout, but have not established the causal connection between these symptoms. These all occurred in a service that creates many (~60) channels on startup, while getting the CDS config over xDS. The service uses grpc-java / grpc-xds `1.83.0`. When we switched it to use mTLS with SPIFFE certificates, we got the following errors: ``` DEADLINE_EXCEEDED: CallOptions deadline exceeded after 4.998s. Name resolution delay 0.000000000 seconds. [closed=[], open=[[connecting_and_lb_delay=4999ms, was_still_waiting]]] ``` ``` io.grpc.StatusException: UNKNOWN at io.grpc.xds.internal.security.DynamicSslContextProvider.onError(DynamicSslContextProvider.java:145) at io.grpc.xds.internal.security.certprovider.CertificateProvider$DistributorWatcher.onError(CertificateProvider.java:128) at io.grpc.xds.internal.security.certprovider.FileWatcherCertificateProvider.checkAndReloadCertificates(FileWatcherCertificateProvider.java:149) Caused by: java.util.ConcurrentModificationException at java.base/java.util.HashMap$HashIterator.nextNode(HashMap.java:1606) at java.base/java.util.HashMap$KeyIterator.next(HashMap.java:1629) at io.grpc.xds.internal.security.certprovider.CertificateProvider$DistributorWatcher.updateSpiffeTrustMap(CertificateProvider.java:120) at io.grpc.xds.internal.security.certprovider.FileWatcherCertificateProvider.checkAndReloadCertificates(FileWatcherCertificateProvider.java:144) ``` ``` java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextNode(HashMap.java:1606) at java.util.HashMap$KeyIterator.next(HashMap.java:1629) at CertificateProvider$DistributorWatcher.onError(CertificateProvider.java:127) at FileWatcherCertificateProvider.checkAndReloadCertificates(FileWatcherCertificateProvider.java:149) ```
ejona86
approved these changes
Oct 19, 2026
kannanjgithub
deleted the
backport-1.85-fix/xds-certificate-watcher-race
branch
October 19, 2026 17:09
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
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.
Backport of #13087 to v1.85.x.
A gRPC client using xDS-driven mTLS does two things concurrently:
The
DistributorWatchersits in the middle and fans out: one cert provider pushes updates to it, and it distributes to N channel watchers.I think there are two conditions in this that can lead to a
ConcurrentModificationException:updateSpiffeTrustMapisn't synchronized (unlikeupdateCertificateandupdateTrustedRoots), so it can race againstaddWatcher/removeWatcherfrom another thread.We observed
ConcurrentModificationExceptioninupdateSpiffeTrustMap()in production, consistent with the unsynchronized iteration described above. We also observed startup RPC deadlines during the rollout, but have not established the causal connection between these symptoms.These all occurred in a service that creates many (~60) channels on startup, while getting the CDS config over xDS. The service uses grpc-java / grpc-xds
1.83.0. When we switched it to use mTLS with SPIFFE certificates, we got the following errors: