Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
1.x
-
None
-
None
Description
Currently user can kill topology directly without waiting for some amount of time so that all inflight messages will get processed. For example, storm is writing to file & user kills topology, file is not closed or moved to proper location. We need to educate operation guys to do the right things also there are some chances that it will be not followed causing system to go in inconsistent state.
Can we set mandatory timeout (configurable) when user kills storm topology? User should not be allowed kill topology with time less than mentioned time.
Some case:
1) If topology is long running don't allow user to kill but time not less than mentioned one
2) If topology is just deployed allow him to kill instantly (as it might be some mistake)
3) Handle same cases from command-line.