-
Type: Bug
-
Resolution: Fixed
-
Priority: Blocker - P1
-
Affects Version/s: None
-
Component/s: None
-
None
-
Atlas Streams
-
Fully Compatible
-
ALL
-
Sprint 51, Sprint 52
A user initiated a stop at 6/13/24 10:05:28.992 PM.
The stop request from Agent<->mongostream failed due to timeout at 6/13/24 10:08:29.013 PM. The user gets a timeout error back.
The executor did not finish shutting down until 6/13/24 10:09:28.930 PM.
This ultimately leaves the processing in a "stopping" state on mongostream, and subsequent stop requests from the customer fail with "Stream processor is already being stopped".
We should investigate why the stop took so long in a separate ticket. In this ticket we should fix the stop flow to fully stop and remove the processor from mongostream, even if the stop request fails due to timeout.
- mentioned in
-
Page Loading...