Management in High Availability Guide

Bug #1643439 reported by fzhylaunchpad
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Won't Fix
Medium
Unassigned

Bug Description

the command is error
# systemctl start mariadb --wsrep-new-cluster

is:
# /usr/libexec/mysqld --wsrep-new-cluster --user=root &

-----------------------------------
Release: 0.0.1 on 2016-11-20 23:55
SHA: 9eff97205f6c5a66419b69a56ac8890c47632e70
Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/ha-guide/source/shared-database-manage.rst
URL: http://docs.openstack.org/ha-guide/shared-database-manage.html

Tags: ha-guide
Chason Chan (chen-xing)
Changed in openstack-manuals:
assignee: nobody → Chason (chen-xing)
Chason Chan (chen-xing)
Changed in openstack-manuals:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-manuals (master)

Fix proposed to branch: master
Review: https://review.openstack.org/404851

Changed in openstack-manuals:
status: Confirmed → In Progress
Revision history for this message
Adam Spiers (adam.spiers) wrote :

No, I think this change to the /usr/libexec/mysqld is wrong for several reasons:

- There is no guarantee that mysqld lives in /usr/libexec on all systems
- There is no guarantee that the startup command is the same on all systems
- It is not OK to bypass systemd or any other init system, since they do a lot more than simply execute the start command (e.g. handling of dependencies and pid files)

Having said that, whilst the proposed fix is wrong, it is probably still correct to report that "systemctl start mariadb --wsrep-new-cluster" fails. So we should not simply close this bug. But it would have been more helpful if the bug report gave the exact error. I expect the problem is that systemctl tries to handle the --wsrep-new-cluster option which should not be there, but I don't have a system to test on right now, so I can't be sure.

Another related question is whether all Linux distributions commonly used for OpenStack now use systemd. I think they do, but I'm not sure. This would determine whether it's OK to use systemctl in OpenStack documentation or whether something more generic like service(8) should be used.

Revision history for this message
KATO Tomoyuki (kato-tomoyuki) wrote :

Should be: # service mysql start --wsrep-new-cluster

Changed in openstack-manuals:
status: In Progress → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on openstack-manuals (master)

Change abandoned by chen.xing (<email address hidden>) on branch: master
Review: https://review.openstack.org/404851

Revision history for this message
Alexandra Settle (alexandra-settle) wrote :

Chen - are you able to update a new patch with the above information?

Revision history for this message
Chason Chan (chen-xing) wrote :
Changed in openstack-manuals:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Change abandoned by Alexandra Settle (<email address hidden>) on branch: master
Review: https://review.openstack.org/404851
Reason: Abandoning due to inactivity and indecision. All discussion for this change should happen in the bug report.

Changed in openstack-manuals:
assignee: Chason (chen-xing) → nobody
status: In Progress → Confirmed
John Chen (cgygyc)
Changed in openstack-manuals:
assignee: nobody → John Chen (cgygyc)
assignee: John Chen (cgygyc) → nobody
Changed in openstack-manuals:
assignee: nobody → foundjem (foundjem-devops)
Chason Chan (chen-xing)
Changed in openstack-manuals:
assignee: foundjem (foundjem-devops) → nobody
Revision history for this message
Frank Kloeker (f-kloeker) wrote :

the doc page don't exists anymore and ha guide is out of openstack-manuals. please refer https://storyboard.openstack.org/#!/project/openstack/ha-guide for new bugs

Changed in openstack-manuals:
status: Confirmed → Won't Fix
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.