Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.1.1
Description
There is a stage in mysqld_safe when it tries to recover mysqld's
database state by starting it with --wsrep-recover. The server is expected
to exit after recovery. After which, mysqld_safe attempts to start the server
again.
However, if server is started using mysqld_safe with wsrep disabled,
mysqld wouldn't terminate post recovery. Due to this init commands
like stop, start won't work as the pid file used to start mysql is different
from what init script expects.
local wr_pidfile="$DATADIR/"`@HOSTNAME@`"-recover.pid"
|
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Assignee | Nirbhay Choubey [ nirbhay_c ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Assignee | Nirbhay Choubey [ nirbhay_c ] | Sergei Golubchik [ serg ] |
Status | In Progress [ 3 ] | In Review [ 10002 ] |
Summary | mysqld should terminate when started with --wsrep-recover | mysqld should auto-terminate when started with --wsrep-recover |
Assignee | Sergei Golubchik [ serg ] | Nirbhay Choubey [ nirbhay_c ] |
Status | In Review [ 10002 ] | Stalled [ 10000 ] |
Resolution | Fixed [ 1 ] | |
Status | Stalled [ 10000 ] | Closed [ 6 ] |
Workflow | MariaDB v2 [ 56713 ] | MariaDB v3 [ 65242 ] |
Workflow | MariaDB v3 [ 65242 ] | MariaDB v4 [ 148368 ] |
http://lists.askmonty.org/pipermail/commits/2014-October/006860.html