You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 30, 2024. It is now read-only.
We currently have tens of thousands of clients connecting to a service running ld-relay. If the SSE connection is closed (e.g. because of a proxy restart or network blip) all clients attempt to reconnect once per second, which hammers our ld-relay service. The reconnect strategy should be configurable, and ideally use exponential backoff with a jitter.
The text was updated successfully, but these errors were encountered:
We'll add this to all our SDKs. For the Java and Android SDKs, this will involve picking up a change to the okhttp-eventsource library: launchdarkly/okhttp-eventsource#7
This has been added to okhttp-eventsource-- one that's released it we'll need a version bump here, and we'll want to expose a configuration parameter for the reconnection timeout at the LDClient config level.
We currently have tens of thousands of clients connecting to a service running ld-relay. If the SSE connection is closed (e.g. because of a proxy restart or network blip) all clients attempt to reconnect once per second, which hammers our ld-relay service. The reconnect strategy should be configurable, and ideally use exponential backoff with a jitter.
The text was updated successfully, but these errors were encountered: