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
Is your feature request related to a problem? Please describe.
When using gRPC plugins, there's no way to specify a timeout. I set the processing time of the plugin too long (over 2 minutes), there will be no response returned even though the gateway has completed the execution.
typeDispatcherinterface {
// Dispatch takes and returns a pointer to a CoProcessMessage struct, see coprocess/api.h for details. This is used by CP bindings.Dispatch(context.Context, *Object) (*Object, error)
...
// Dispatch takes a CoProcessMessage and sends it to the CP.func (d*GRPCDispatcher) Dispatch(ctx context.Context, object*coprocess.Object) (*coprocess.Object, error) {
returngrpcClient.Dispatch(ctx, object)
}
The text was updated successfully, but these errors were encountered:
I'm sorry for the slow acknowledgement here - thank you for your suggestion and PR. It seems like a reasonable capability to add to Tyk, we'll take a look at this and will let you know if and when we can add it to the product.
Thanks again for your contribution!
andyo-tyk
changed the title
There is no timeout in the gRPC plugin coprocess
[TT-10277] There is no timeout in the gRPC plugin coprocess
Oct 17, 2023
Is your feature request related to a problem? Please describe.
When using gRPC plugins, there's no way to specify a timeout. I set the processing time of the plugin too long (over 2 minutes), there will be no response returned even though the gateway has completed the execution.
Describe the solution you'd like
timeout
field (second)timeout
fieldcontext.Context
paramterGRPCDispatcher (and PythonDispatcher) implement Dispatch, add ctx parameter
The text was updated successfully, but these errors were encountered: