Bug #71807 Help message is not formatted properly
Submitted: 23 Feb 2014 11:29 Modified: 30 Sep 2015 1:30
Reporter: Alfranio Tavares Correia Junior Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Fabric Severity:S3 (Non-critical)
Version:1.4.1 OS:Any
Assigned to: CPU Architecture:Any

[23 Feb 2014 11:29] Alfranio Tavares Correia Junior
Description:
Help message is not formatted properly.

How to repeat:
Execute the "mysqlfabric help group command". For example,

$ mysqlfabric help group promote
group promote group_id  [--SLAVE_UUID=NONE] [--UPDATE_ONLY=FALSE] [--SYNCHRONOUS=TRUE]  

Promote a server into master.

If users just want to update the state store and skip provisioning
steps     such as configuring replication, the update_only parameter
must be set to     true. Otherwise, the following happens.

If the master within a group fails, a new master is either
automatically     or manually selected among the slaves in the group.
The process of     selecting and setting up a new master after
detecting that the current     master failed is known as failover.

It is also possible to switch to a new master when the current one is
still     alive and kicking. The process is known as switchover and
may be used, for     example, when one wants to take the current
master off-line for     maintenance.

If a slave is not provided, the best candidate to become the new
master is     found. Any candidate must have the binary log enabled,
should     have logged the updates executed through the SQL Thread and
both     candidate and master must belong to the same group. The
smaller the lag     between slave and the master the better. So the
candidate which satisfies     the requirements and has the smaller lag
is chosen to become the new     master.

In the failover operation, after choosing a candidate, one makes the
slaves     point to the new master and updates the state store setting
the new master.

In the switchover operation, after choosing a candidate, any write
access     to the current master is disabled and the slaves are
synchronized with it.     Failures during the synchronization that do
not involve the candidate slave     are ignored. Then slaves are
stopped and configured to point to the new     master and the state
store is updated setting the new master.

Suggested fix:
Format messages properly
[30 Sep 2015 1:30] Philip Olson
Posted by developer:
 
Fixed as of the upcoming MySQL Fabric 1.6.2 release, and here's the changelog entry:

The mysqlfabric help text formatting was improved.

Thank you for the bug report.