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
I have process that requires a sequence of calls via GRPC, this process involves 3 different systems:
A
B
C
They are connected following the dag: A->B->C, via synchronous blocking calls.
The question
I want to set a tighter deadline in the request between A->B than the time that it might require B to fulfill the request. If the deadline is reached, I would like B to continue processing the request.
This can be achieved if B keeps processing the request even after the deadline. My question relates to the automatic propagation of the deadlines, because I'm wondering if the deadline set in A->B, can be automatically propagated to the request B->C, generating an issue in the process being executed in B cancelling its execution
The application's environment
Which versions do you use?
Spring (boot): 3.3.4
grpc-java: 1.68.0
grpc-spring-boot-starter: 3.1.0
java: version + architecture (64bit?) 21-zulu
Other relevant libraries...
The text was updated successfully, but these errors were encountered:
The context
I have process that requires a sequence of calls via GRPC, this process involves 3 different systems:
They are connected following the dag: A->B->C, via synchronous blocking calls.
The question
I want to set a tighter deadline in the request between A->B than the time that it might require B to fulfill the request. If the deadline is reached, I would like B to continue processing the request.
This can be achieved if B keeps processing the request even after the deadline. My question relates to the automatic propagation of the deadlines, because I'm wondering if the deadline set in A->B, can be automatically propagated to the request B->C, generating an issue in the process being executed in B cancelling its execution
The application's environment
Which versions do you use?
The text was updated successfully, but these errors were encountered: