A batch workflow containing a Kafka Collection Agent collection agent will remain in RUNNING mode running state and wait for more data even if there is no more data to consume, and await more data. This is a major difference from compared to how batch workflows behave for other collection agents ; they which will STOP stop when the data from the last start cycle has been consumed, see Workflow Monitor (4.2) for more information about workflow execution states. Note also that a
Note!
A batch will not be completed if:
the configured Batch Size has not been reached
...
ora
...
hardcoded timeout of five (5) seconds has not been reached.
A Kafka collection workflow must be stopped by other means as it is never stopped automatically. It can will only stop automatically if it is aborted aborts due to errors. Stopping a workflow can be done through:
The user interface.
Command line interface mzsh.
Operational REST interface.
A workflow stop can also be triggered autromatically by evaluating MIMs like Workflow Throughput and Estimated Lag - where no lag means that there is no data left to process.
...
.
During other circumstances you can stop it via:
Desktop Online
mzcli.
the operational REST interface.
Note!
The 5 second timeout for completing a batch also applies when stopping a Kafka batch collection workflow through these interfaces.