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
{{ message }}
This repository was archived by the owner on Oct 23, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -331,7 +331,7 @@ A `KinesisConsumer` is used internally for the `Kinesis.source`. All rules descr
331
331
### Graceful Shutdown
332
332
333
333
Currently the KinesisConsumer Shutdown works as follows:
334
-
*Shutdown is called on the `KinesisConsumer` (either explicitly or via the jvm shutdown hook)
334
+
*`stop()` is called on the `KinesisConsumer` (either explicitly or via the jvm shutdown hook)
335
335
* This then calls `requestShutdown` on the KCL Worker, blocking until completion.
336
336
* The KCL Worker propagates this down to the `ConsumerProcessingManager` (Which is the `IRecordProcessor`) - calling `shutdownRequested` on each instance (one per shard).
337
337
* When `shutdownRequested` is called, this sends a `GracefulShutdown` message to the `ConsumerWorker` Actor, blocking until a response is received (Ask + Await).
0 commit comments