-
Notifications
You must be signed in to change notification settings - Fork 759
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: query flight rpc connection leaking #13956
Conversation
Docker Image for PR
|
This comment was marked as outdated.
This comment was marked as outdated.
Docker Image for PR
|
This comment was marked as outdated.
This comment was marked as outdated.
e670fbe
to
07877b8
Compare
Docker Image for PR
|
This comment was marked as outdated.
This comment was marked as outdated.
Docker Image for PR
|
This comment was marked as outdated.
This comment was marked as outdated.
Docker Image for PR
|
This comment was marked as outdated.
This comment was marked as outdated.
Docker Image for PR
|
This comment was marked as outdated.
This comment was marked as outdated.
instead of `notify_waiters`, so that the task spawned in `streaming_receiver` shall not missed the notification, even if the notification is sent before waiting
5e768a8
to
1882159
Compare
This reverts commit 6a0dbe6.
4222384
to
831c185
Compare
Docker Image for PR
|
Docker Image for PR
|
Pull request description must contain CLA like the following:
|
I hereby agree to the terms of the CLA available at: https://databend.rs/dev/policies/cla/
Summary
fix rpc connection leak:
use the current runtime while building
FlightExchange::Receiver
in flight_clientintroduce
WatchNotify
which provides the similar functionality of
Notify
, excepts that it allowsnotify_waiters
be called beforeNotified
future is instantiated or being polled, without losing wakeups.It replaced the
Notify
used in flight_client, andExecutorTasksQueue
,PipelineExecutor
andRangeJoinState
Closes #issue
This change is