| 387 | In this second demo we will be starting the Self-healing service and repeat the node failure simulation. |
| 388 | |
| 389 | At the service's startup, it loads the config file and recognizes the resources that it needs to monitor: |
| 390 | |
| 391 | [[Image(sh-service startup.png, center)]] |
| 392 | |
| 393 | We repeat the node failure several times. In the screenshot you may see that node failure was repeated three times, but each time the self-healing service starts the service on a node to fill-in for the missing information. Only once the node failure was so close to the client's request that the latter could only read 1 value. The other times, the nodes were up again in time for the client to read enough values: |
| 394 | |
| 395 | [[Image(sh-start node.png, center)]] |
| 396 | |