[MDEV-27669] Not possible to check whether a server was started with skip-slave-start option Created: 2022-01-28 Updated: 2024-02-06 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | None |
| Fix Version/s: | 11.6 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Hartmut Holzgraefe | Assignee: | Sergei Golubchik |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
When a slave does not start up the slave threads on restart, but not reporting anything to the error log about startup failures either, this can be due to skip-slave-start being set in the config file(s) or on the command line (and most likely is). But as there is no matching variable in SHOW VARIABLES or SHOW SLAVE STATUS output this can't be checked for at runtime from the SQL level, and there is no related message in the error log either. I'd request to at least have a message like "Skipping slave start as requested" written to the error log when skip-slave-start is in effect, but would actually prefer to have a proper variable entry for this so that GLOBAL_VALUE_ORIGIN and GLOBAL_VALUE_PATH can be checked for this setting in INFORMATION_SCHEMA.SYSTEM_VARIABLES |
| Comments |
| Comment by Sergei Golubchik [ 2023-12-01 ] |
|
It's, of course, doable. Should it print only command line options or also settings from my.cnf? The latter could be a very long list. I think it'd be simpler and less controversial to do what Hartmut suggested,
|
| Comment by Ralf Gebhardt [ 2024-02-06 ] |
|
serg, I agree that to print settings from my.cnf makes it a too long list. So lets go with a message like suggested by hholzgra . I still would like to extent the task to at least cover:
I do not know if all used "skip" options are handled at one place in the code, which would make it easy to just print a line for anything skipped. |