Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.3.17
-
None
Description
Hi,
I just upgraded a slave of a 10.3.15 from 10.3.15 to 10.3.17. Now I cannot shutdown the database or stop the slave threads, if they are running (I need to use kill -9).
When I start the database with skip_slave_start, I can shutdown the database normally.
When I start only the IO_THREAD or only the SQL_THREAD, stop slave works.
When I start all threads, neither stopping them or shutting down the whole database works.
However, when the master is not reachable when starting the slave threads, stopping them is possible.
When the master is shut down while the slave threads are running, stopping the threads will not work. show slave status shows:
Slave_SQL_Running_State: Waiting for worker threads to be idle
|
Please let me know if you need further information.
Cheers,
Volker
Attachments
Issue Links
- is duplicated by
-
MDEV-20247 Replication hangs with "preparing" and never starts
-
- Closed
-
It could be related to
MDEV-20247.Do you use any non-zero value of innodb-thread-concurrency? Try to disable it and see if the problem goes away.
Also, if you get a readable stack trace of all threads from the hanging slave, we'll probably be able to tell with more certainty. But if you indeed use the value and disabling it helps, with all likelihood it's the same problem.