This shows you the differences between two versions of the page.
ii:labs:s2:05:tasks:03 [2022/05/31 15:29] radu.ciobanu |
ii:labs:s2:05:tasks:03 [2024/04/29 18:43] (current) radu.ciobanu |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ==== 03. [30p] Handling failures in a multi-node Docker Swarm cluster ==== | + | ==== 03. [10p] Testing for data persistence ==== |
- | + | ||
- | In this exercise, we will see what happens when one of the worker nodes crashes. | + | |
== Subtasks == | == Subtasks == | ||
- | - stop //**node2**// by clicking on it in the left-hand side of the Play with Docker page, and then clicking the orange //**Delete**// button | + | - stop and delete the three containers started at exercise 1 |
- | - quickly go back to the //**visualizer**// page and see what happens; what do you see? what happens to //**node2**//? what happens to the services that were running on //**node2**//? | + | - start them again using the same commands given at exercise 1 |
- | + | - send a //**POST**// request using Postman and verify that the book you added at exercise 2 is still in the library | |
- | == What to upload == | + | |
- | + | ||
- | * a print screen with the //**visualizer**// page after having stopped //**node2**// | + |