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
RSCBC-249: move close-watcher setup into successful connection path
Move the on_close channel and close-watcher task in begin_client_build
from being created once before the retry loop to being created inside
the success path of each retry iteration.
Previously, if a connection attempt failed during bootstrap (e.g. auth
or bucket select failure), StdKvClient::new would call kv_cli.close(),
which fired the on_close_tx signal. This prematurely woke the
close-watcher task, which saw no client in state and exited permanently.
When the retry loop eventually succeeded and that client later
disconnected, no close-watcher existed to detect it and trigger
reconnection.
Now each retry iteration creates its own channel and client ID, and the
close-watcher is only spawned after a successful connection. Failed
attempts' channels are simply dropped with no side effects.
0 commit comments