Bosh resurrector plugin is a tool used to recreate the vm if it is not in running state. More details available at https://bosh.io/docs/resurrector/
Bosh has an agent running on each vm, if the agent does not respond to a heart beat every minute, bosh will mark vm unresponsive and will try to recreate it. If one of vm processes is failing, the vm will be marked as falling state and resurrector will try to fix it by recreating the vm.
Resurrection can be enabled globally or per deployment basis.
To enable resurrection globally:
To enable resurrection on per deployment basis follow these steps:
1. Create a resurrection.yaml config file with the following content:
rules: - enabled: false include: deployments: - "deployment-abc"
2. Apply the bosh config to the deployment:
bosh update-config --type resurrection --name deployment-abc resurrection.yaml
To remove a resurrection setting from a deployment, run the following commands
bosh configs
Find the resurrection config you applied and then delete it:
bosh delete-config <config ID>
Note: Command bosh curl /resurrection shows the global status of the setting. To a get a per deployment status, check if the resurrection config file exists for the deployment.
Note: there is an issue with the setting, described in this KB Bosh resurrector not working after deleting a resurrection config (89164) https://broadcomcms-software-agent.wolkenservicedesk.com/wolken/esd/knowledge-base-view/view-kb-article?articleNumber=313132