Skip to main content Skip to complementary content

Running the graceful shutdown process of Remote Engine

Use the graceful shutdown command to ensure a controlled and orderly shutdown process.

Before you begin

  • Your Remote Engine version must be v2.12.14 onwards.


In your Karaf command line console, run the following command:
tre:graceful-shutdown <shutdown_grace_period_in_minutes>
In this command, define the shutdown grace period for the engine, specified in minutes, before it is eventually shut down. This shutdown grace period is a shutdown delay time. For example,
tre:graceful-shutdown 1
In this example, the command waits for 1 minute before shutting down your Remote Engine.


Screenshot showing the Karaf console running the graceful shutdown process of Remote Engine.


When the command is launched, your engine enters the grace period (the shutdown delay period) where it rejects any new data integration tasks and simultaneously, scans all active task runs, that is to say, all running executions. As the grace period reaches its end, the engine proceeds to appropriately terminate the running executions of all the data integration tasks and ensure that the Terminated status is correctly labeled.

The graceful shutdown process does not affect the data service tasks or the Route tasks, which include microservices and OSGi services. The microservices continue to run, with no impact from the grace period, until they are terminated along with the engine shutdown, and they are automatically resumed upon the engine restart. The OSGi services, which are deployed on Talend Runtime, keep running separately on that server.

More commands are available to help understand the situation of your engine and the task runs on it:
  • tre:info: obtain a list of task types assigned to your engine.
  • tre:execution-list: list all task runs on your engine.
  • tre:execution-info: check details of a specific run.
  • tre:execution-kill: kill a task run without restarting the engine.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!