BigData / Apache StreamPark Interview questions
Explain the lifecycle of a StreamPark Application from creation to termination?
A StreamPark "Application" moves through a well-defined set of states, and understanding the flow makes it easier to reason about where a stuck job actually is.
An Application starts as a configuration record: development mode, execution mode, Flink version, and parameters, tied to either an uploaded jar or Flink SQL. If it uses Project Management, it moves through a build stage before it's runnable. Starting it hands control to the relevant Flink Submit implementation, and a successful submission moves it to Running, where StreamPark polls the cluster for live status.
From Running, the application can be savepointed (state captured without stopping), stopped (optionally with a final savepoint for a clean restart later), or fail on the cluster, which is reported back and can trigger alerts. Restarting a stopped or failed Application typically resumes from its last savepoint rather than starting the state fresh, closing the loop back to Running.
More Related questions...