In some rare cases (especially related to emergency situations in env) we can see that one or more of workflows have “in progress” status, however there no any launched sub-steps (streams). For example:
Note: please do not confuse it with hanging extract-stream. In that case: we are able to expand workflow line in MT and see that there is stream in processing state (not workflow).
This page with help you unstuck the process using built-in EJM instruments:
| Table of Contents |
|---|
Reset Sequencer Using eagle_ml-2-0_default_cm_sequencer_cleanup
Reset current stuck process
Reset the entire queue
...
In case of sequencer getting stuck, we suggest checking estar/tpe/cfg/msgcenter/msgservice.ini config file first of all.
SplitBatchSize parameter should not be a large number, preferred value is 2, in some cases, 1 - it is responsible for memory consumption and values like 100 may harm processing.
In case of sequencer getting stuck, our cleanup stream can work in several modes - either remove the entire queue or remove only the current (stuck workflow, including the case when you use PROCSEQID). Command:
| Code Block | ||
|---|---|---|
| ||
1176:CUR_eagle_wrf_generic_load:1177:INTRADAY: |
unstucks it.