You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem description:
Currently we are facing the issue that if we run a task application via kubernetes - the node can be restarted at any time. This causes all pods to be terminated. In this case we have no way to check it and the task remain on status "running", but nothing is happening anymore.
Since we are using Spring Batch we can use a query towards the batch database and check if the task application is still running and no update for the batch job has occurred for a defined time span. (database column name: last_updated)
Solution description:
Improve the REST endpoint to get the task status to also check via Spring Cloud Deployer if the task application is still running in the infrastructure:
If the task application is not running anymore but in the task database it is still mentioned as running you could return a specific task status to handle this issue.
Description of alternatives:
N/A
Additional context:
N/A
The text was updated successfully, but these errors were encountered:
Problem description:
Currently we are facing the issue that if we run a task application via kubernetes - the node can be restarted at any time. This causes all pods to be terminated. In this case we have no way to check it and the task remain on status "running", but nothing is happening anymore.
Since we are using Spring Batch we can use a query towards the batch database and check if the task application is still running and no update for the batch job has occurred for a defined time span. (database column name:
last_updated
)Solution description:
Improve the REST endpoint to get the task status to also check via Spring Cloud Deployer if the task application is still running in the infrastructure:
If the task application is not running anymore but in the task database it is still mentioned as running you could return a specific task status to handle this issue.
Description of alternatives:
N/A
Additional context:
N/A
The text was updated successfully, but these errors were encountered: