Pacemaker doesn't wait for innobackupex-apply finish
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Vladimir Kuklin | ||
Mitaka |
Fix Released
|
High
|
Gabor Orosz | ||
Newton |
Fix Committed
|
High
|
Vladimir Kuklin |
Bug Description
=== Environment ===
Release: MOS 9.0 (build #507, 12/12-2016)
Plugins: Zabbix
Features: Reduced Footprint
=== Description ===
After reboot/failure of one Controller node, MySQL database sync is started
Under some circumstances (big size of the database, slow hardware, etc) the applying InnoDB log files might take longer than usual
If it takes longer than the resource timeout, then Pacemaker kills the MySQL process
=== Actual behavior ===
Pacemaker kills the MySQL process and the applying stage will never end
2017-01-
2017-01-
2017-01-
2017-01-
2017-01-
2017-01-
2017-01-
Eventually, MySQL on this node ends up having inconsistent state of InnoDB log and can't start without manual intervention anymore
2017-01-
2017-01-
2017-01-
2017-01-
2017-01-
=== Expected behavior ===
Please add the logic in OCF script which checks that the innobackupex-apply is still in progress and don't let Pacemaker kill MySQL process
(something similar is implemented with regards to SST process: https:/
=== Attachments ===
I'm not allowed to upload customer's log files here
If MySQL/Pacemaker logs are required, I can show them privately
Changed in fuel: | |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
Changed in fuel: | |
status: | New → Confirmed |
milestone: | 9.2 → 11.0 |
tags: | added: area-library |
tags: | added: on-verification |
Fix proposed to branch: stable/mitaka /review. openstack. org/429787
Review: https:/