| 1 |
Setup error insert to interleave DEFINE_BACKUP_REQ replies with NODE_FAILREP |
| 2 |
|
| 3 |
Start backup, that will fail due to node failure |
| 4 |
Wait for cluster to come up again |
| 5 |
Node 143: STARTED |
| 6 |
Node 144: STARTED |
| 7 |
Setup error insert to interleave START_BACKUP_REQ replies with NODE_FAILREP |
| 8 |
|
| 9 |
Start backup, that will fail due to node failure |
| 10 |
Wait for cluster to come up again |
| 11 |
Node 143: STARTED |
| 12 |
Node 144: STARTED |
| 13 |
Setup error insert to interleave STOP_BACKUP_REQ replies with NODE_FAILREP |
| 14 |
|
| 15 |
Start backup, that will fail due to node failure |
| 16 |
Wait for cluster to come up again |
| 17 |
Node 143: STARTED |
| 18 |
Node 144: STARTED |
| 19 |
Setup error insert so that backup fails in a controlled way |
| 20 |
|
| 21 |
Start backup, that will fail due to node failure |
| 22 |
Check that node failure was controlled (e.g. node recovers) |
| 23 |
Node 143: STARTED |
| 24 |
Node 144: STARTED |
| 25 |
Node recovered, ok |
| 26 |
Clear error |
| 27 |
|
| 28 |
Check backup ok |
| 29 |
Setup error insert so that backup fails due to illegal signal |
| 30 |
a) Error insert causes Backup 1 to set (restrict) signal scope |
| 31 |
b) Backup 1 is run (succesfully) setting signal scope for BACKUP_REQ |
| 32 |
c) Backup 2 is run subject to signal scope, and causes crash |
| 33 |
in master data node when BACKUP_REQ is received from MGMD. |
| 34 |
The expectation is: |
| 35 |
- The master node will fail |
| 36 |
- Other nodes will be unaffected |
| 37 |
|
| 38 |
Run a backup (and set up error insert) |
| 39 |
Start backup again, that will fail due to node failure |
| 40 |
Check that node failure was controlled (e.g. node recovers) |
| 41 |
Node 143: STARTED |
| 42 |
Node 144: STARTED |
| 43 |
Node recovered, ok |
| 44 |
Clear error |
| 45 |
|
| 46 |
Check backup ok |