-
Notifications
You must be signed in to change notification settings - Fork 590
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
Can't close Gateway with ongoing requests #1518
Comments
ProblemThis is not related to job workers but in general if there is an ongoing request during shutdown. The reason for this is the order in which we shutdown our components:
The Possible solutionNo matter what solution we choose we have to close the gRPC server before closing the broker client in the gateway. As the client is required to complete the ongoing requests. This will at least ensure that requests timeout and the server can terminate, even if the stream processors are already shutdown. As a quick dirty workaround we can use |
chore(qa): remove topic subscription from it tests * replace in most test cases the ClientRule with the GrpcClientRule * rename ClientRule to GatewayRule * create AssertionHelper for the usage of the RecordExporter * #1518 ignores some tests where gateway can't be closed * to remove gateway from clustering rule etc we have to do this #1520 closes #1512 closes #1525
1763: fix(broker-core): close gateway before service containers r=MiguelPires a=MiguelPires The gateway was being closed after the service containers so it would hang since these would never terminate. I separated the gateway's resource releasing delegate from the others, so we could close it before the service containers. closes #1518 Co-authored-by: Miguel Pires <miguel.pires@camunda.com>
There are still some tests ignored |
Scenario:
If we remove line 2 and 3 it works.
The text was updated successfully, but these errors were encountered: