mysqld hangs on shutdown

Bug #529245 reported by Alex Yurchenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Fix Released
High
Seppo Jaakola
0.7
Fix Released
High
Seppo Jaakola

Bug Description

After successfully setting wsrep provider from mysql client mysqld refuses to shutdown:

Feb 27 22:21:59 mysqlxxx mysqld: 100227 22:21:59 [Note] WSREP: New cluster view: group UUID: 85ce3153-23ee-11df-0800-fdfff916b53b, conf# 1: Primary, number of nodes: 1, my index: 0, first seqno: 1
Feb 27 22:28:02 mysqlxxx mysqld: 100227 22:28:02 [Note] /usr/libexec/mysqld: Normal shutdown
Feb 27 22:28:02 mysqlxxx mysqld:
Feb 27 22:28:02 mysqlxxx mysqld: 100227 22:28:02 [Note] Event Scheduler: Purging the queue. 0 events
Feb 27 22:28:02 mysqlxxx mysqld: 100227 22:28:02 [Note] wsrep closing connection to cluster
Feb 27 22:28:02 mysqlxxx mysqld: 100227 22:28:02 [Warning] WSREP: Waiting for 1 items to be fetched.
Feb 27 22:28:02 mysqlxxx mysqld: 100227 22:28:02 [Note] WSREP: rollbacker thread exiting
Feb 27 22:28:02 mysqlxxx mysqld: 100227 22:28:02 [Note] WSREP: Received self-leave message.
Feb 27 22:28:02 mysqlxxx mysqld: 100227 22:28:02 [Note] WSREP: Flow-control interval: [-4611686018427387904, -9223372036854775808]
Feb 27 22:28:02 mysqlxxx mysqld: 100227 22:28:02 [Note] WSREP: Received SELF-LEAVE. Closing connection.
Feb 27 22:28:02 mysqlxxx mysqld: 100227 22:28:02 [Note] WSREP: Shifting SYNCED -> CLOSED (TO: 0)
Feb 27 22:28:02 mysqlxxx mysqld: 100227 22:28:02 [Note] WSREP: RECV thread exiting 0: Success
Feb 27 22:28:02 mysqlxxx mysqld: 100227 22:28:02 [Note] WSREP: New NON-PRIMARY configuration: -1, seqno: 0, group UUID: 85ce3153-23ee-11df-0800-fdfff916b53b, members: 0, my idx: -1
Feb 27 22:28:02 mysqlxxx mysqld: 100227 22:28:02 [Note] WSREP: recv_thread() joined.
Feb 27 22:28:02 mysqlxxx mysqld: 100227 22:28:02 [Note] WSREP: Closing slave action queue.
Feb 27 22:28:02 mysqlxxx mysqld: 100227 22:28:02 [Note] WSREP: Closed GCS connection
Feb 27 22:28:02 mysqlxxx mysqld: 100227 22:28:02 [Note] WSREP: New cluster view: group UUID: 85ce3153-23ee-11df-0800-fdfff916b53b, conf# -1: non-Primary, number of nodes: 0, my index: -1, first seqno: 1
Feb 27 22:28:05 mysqlxxx mysqld: 100227 22:28:05 [Note] WSREP: gcs_recv() returned -77 (File descriptor in bad state)
Feb 27 22:28:05 mysqlxxx mysqld: 100227 22:28:05 [Note] wsrep recv thread exiting (code:5)

Silence after that

Changed in codership-mysql:
importance: Undecided → High
assignee: nobody → Seppo Jaakola (seppo-jaakola)
milestone: none → 0.7.3
Changed in codership-mysql:
status: New → Incomplete
Revision history for this message
Seppo Jaakola (seppo-jaakola) wrote :

This issue lacks detailed steps to reproduce, and nothing like this has been observed when testing with current head version.

Most likely the underlying issues has been cured in fixes for lp:529883, lp:534914 and lp:513268

Changed in codership-mysql:
status: Incomplete → Fix Committed
Changed in codership-mysql:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.