Reputation: 843
I am using Spring Cloud Dataflow Server 2.9.6 to run a composed task on Kubernetes. The individual tasks run fine and terminate. The composed task runner, however does not terminate. The pod stays alive.
I noticed, that for a similar task, that is launched via task launcher stream application, the compound task runner terminates as expected when I pass the command line argument --spring.cloud.task.closecontextEnabled=true
in the task launch request.
I did not manage to set that variable from the UI when manually launching a composed task.
In the docs, there is a separate section for Ctr Properties, see here: https://dataflow.spring.io/docs/2.9.x/feature-guides/batch/composed-task/#launch-the-composed-task-definition There is a composed-task-app-properties
to set in the doc's screen shot. But for me, this section is not showing when launching the composed task.
Is there a way for setting the composed task runner arguments from the UI? Or is there a way to set this automatically? For me, it does not make sense to keep the CTR process alive by default. What's the reason for this?
Upvotes: 0
Views: 302