Meter statuses
Understand meter run statuses.
A meter status indicates the current state of a meter's execution. The status displayed in the UI reflects the latest execution state of the meter. Streaming and batch meters use some different statuses because streaming meters process incoming events continuously, while batch meters process a finite set of input data.
Meter run statuses
| Status | Applies to | Description |
|---|---|---|
| Never Run | Streaming and batch | The meter has been created but has not yet been started. |
| Job Submission In Progress | Streaming and batch | The run request has been accepted and the meter is being prepared for execution. |
| Initializing | Streaming and batch | The meter is starting and preparing resources before processing begins. |
| Running | Streaming and batch | The meter is actively processing data. |
| Stopping | Streaming | A graceful stop has been requested and the streaming meter is shutting down. |
| Paused | Streaming | Processing has stopped gracefully. A streaming meter in this state can be started again to resume processing. |
| Stopped | Batch | Processing was canceled before completion. This is the stopped state displayed for a batch meter. |
| Failed | Streaming and batch | The meter encountered an error and stopped processing. |
| Processing Completed | Batch | The meter successfully finished processing all available input data. |
| Sending Output | Batch | The meter has completed input processing and is sending output to downstream systems. |
| Processing Output | Batch | Output has been sent and downstream processing is still in progress. |
| Consume Completed | Batch | All downstream processing has completed successfully. |
Test-run statuses
Test-run statuses apply only to test or debug runs. They do not affect the execution state of a normal production run.
| Status | Description |
|---|---|
| Testing | A test run is currently executing. |
| Testing Passed | The test completed successfully. |
| Testing Failed | The test completed with errors. |
Streaming meter lifecycle
Streaming meters continuously process incoming events and remain active until they are explicitly stopped.
Never Run -> Job Submission In Progress -> Initializing -> Running -> Stopping -> Paused
- Streaming meters normally remain in Running while they process incoming events.
- Stopping indicates that a graceful stop has been requested.
- After a successful graceful stop, the meter changes to Paused.
- A paused streaming meter can be started again to resume processing.
- Streaming meters do not normally reach Processing Completed because they continuously process new events.
Batch meter lifecycle
Batch meters process a finite set of input data and automatically complete after all available input has been processed.
Never Run -> Job Submission In Progress -> Initializing -> Running -> Processing Completed -> Sending Output -> Processing Output -> Consume Completed
- Batch meters process a bounded set of input data.
- After input processing completes, output processing can continue through Sending Output, Processing Output, and Consume Completed.
- If a batch meter is manually stopped before processing completes, its UI status is Stopped.
- If processing fails, the status is Failed.
- Starting a stopped batch meter creates a new execution.
Streaming and batch meter behavior
| Behaviour | Streaming Meter | Batch Meter |
|---|---|---|
| Normal long-running state | Running | Running |
| Natural completion | Does not normally complete automatically. | Processing Completed |
| Graceful stop | Stopping -> Paused | Not applicable. |
| Manual cancellation | Paused | Stopped |
| Output processing | Not typically applicable | Sending Output -> Processing Output -> Consume Completed |