Storing Failed Containers
The platform provides a possibility to temporarily store (rather than just remove) environment nodes if their creation has failed, including a failure during redeploy. Such behavior helps with the analysis of the occurred problem, allowing to fix it and avoid similar issues in the future. Obviously, the failed containers will be properly unbound from the user account, avoiding the unfair client balance charges.
To enable this functionality on the platform, the following two system settings are used:
- jelastic.node.failed.persist.enabled - enables (true) or disables (false, by default) the storing of the failed nodes
- jelastic.node.failed.persist.days - sets a number of days (7, by default) to keep the failed containers before automatically remove them with the qjob.delete_illegal_containers.cron_schedule job
