[MDEV-29412] galera new cluster Created: 2022-08-30 Updated: 2022-10-03 Resolved: 2022-10-03 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera |
| Affects Version/s: | 10.3, 10.4, 10.5, 10.6, 10.7, 10.8, 10.9, 10.10 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Minor |
| Reporter: | Sylvain ARBAUDIE | Assignee: | Jan Lindström (Inactive) |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Description |
|
the bootstrap script galera_new_cluster execute a restart command. this is dangerous as it means one can create a new cluster alsmot without cotrol out of a percectly functionning node. imo galera_new_cluster should only trigger a start command, forcing a ,manual stop as a security pre step. i understand security comes from the grastate.dat ready-to-bootstrap features. yet this leaves you with a stopped node which will need to resync while having to manually stop the node should make operative thinnk twice about the necessity to bootstrap this particular node. |
| Comments |
| Comment by Jan Lindström (Inactive) [ 2022-10-03 ] |
|
SylvainArbaudie I agree on your reasoning. However, changing scrip behavior in GA-releases is also problematic as user's have used this script as it is provided and changing it will break current expected behavior. Remember that galera_new_cluster is just a script and if you require different behavior for security reasons you may edit it. |