Flink service management via ADCM
The ADCM UI provides actions to manage the Flink service and its components. For information on how to run service actions, refer to ADH service actions.
The actions available for the Flink service are listed in the table below.
Action | Description |
---|---|
Check |
Runs service-specific tests to check the health of the service and its components |
Start |
Starts the service.
When you run this action, the option Apply configs from ADCM is available.
If it is set to |
Stop |
Stops the service |
Restart |
Restarts the service.
When you run this action, the option Apply configs from ADCM is available.
If it is set to |
Remove |
Removes the service from the cluster. This action should be used to remove already installed services. Whereas the control can be used to remove a non-mapped service (a service which components have not been distributed among cluster hosts) |
Add Client(s) |
Adds Flink client(s) to the cluster. Running this action opens the component-host mapping interface where you can add new Flink clients |
Remove Client(s) |
Removes Flink client(s) from cluster hosts. Running this action opens the component-host mapping interface where you can remove Flink clients from specific hosts |
Add JobManager(s) |
Adds Flink JobManager components. Running this action opens the component-host mapping interface where you can add new JobManager components |
Move Flink JobManager |
Moves the Flink JobManager component to a different host. Use the force option if the source host (where the component is currently installed) is offline |
Remove JobManager(s) |
Removes Flink JobManager components. Running this action opens the component-host mapping interface where you can remove JobManager components |
Add TaskManager(s) |
Adds Flink TaskManager components. Running this action opens the component-host mapping interface where you can add new TaskManager components |
Remove TaskManager(s) |
Removes Flink TaskManager components. Running this action opens the component-host mapping interface where you can remove TaskManager components |