Closed jsa4000 closed 5 years ago
@jsa4000 in your application properties, can you try setting spring.cloud.task.closecontext_enabled
to true
? (https://docs.spring.io/spring-cloud-task/docs/current-SNAPSHOT/reference/html/features-lifecycle.html)
@chrisjs Thanks for your response.
That is exactly what I did, however I dunno the drawbacks of doing that since it is not enabled by default. It seems more like a workaround rathen a solution.
If it is not the case then this flag surely works for me. I would put into the documentation for everyone else. :)
@jsa4000 https://spring.io/blog/2018/02/14/spring-cloud-task-2-0-0-m3-is-now-available in the "Update To An Important Default" section provides a little more info, where true
used to be the default. as its a spring cloud task property, its located in the task docs link above. for additional details you may want to ping on the task gitter channel: https://gitter.im/spring-cloud/spring-cloud-task
Thanks for the links and for the support. Really appreciated.
Hello,
I am experiencing an issue running jobs using Spring Batch processing with partitions (master/slave) using spring-cloud-deployer-kubernetes.
To put some context, following is the environment I have used:
v1.10.11
v1.11.9
springcloud/spring-cloud-dataflow-server:2.0.0.RELEASE
org.springframework.cloud:spring-cloud-deployer-kubernetes:2.0.1.RELEASE
When I launch the task, the job is processed correctly, however the Pods still running forever. Both master and slave, hangs on
o.s.c.t.r.support.SimpleTaskRepository : Updating: TaskExecution with executionId=9 with the following...
. However, when I run the same job using the local deployer, all instanciated java applications (master and slaves) exit successfully. I have tested tasklets and run correctly in k8s, showing the Completed (0/1) status, however using partitions is not the same expected behaviour.The steps are very straightforward:
Following is the output using the shell.
However, when I print out the pods currently running (here, I have run the same job more that once):
And those are the logs:
The code can be seen in my github repo.
Thanks in advance
Javier