Bug #55697 "start process" help text doesn't properly account for extending a Cluster

• Submitted: 2 Aug 2010 19:15
• Modified: 6 Aug 2010 9:52
• Reporter: Andrew Morgan
• Status: Closed
• Category: MySQL Cluster Manager: CLI
• Severity: S3 (Non-critical)
• Version: MCM1.1
• OS: Any
• Assigned to: Sivert Sørumgård
• CPU Architecture: Any

[2 Aug 2010 19:15] Andrew Morgan

Description:
The help text for start process doesn't really fit with the new capability to add new nodes to an existing Cluster. 

mcm> start process --help;

+--------------------------------------------------------------------------------------------------+
| Help                                                                                             |
+--------------------------------------------------------------------------------------------------+
|                                                                                                  |
| start process [options] <processid> <clustername>                                                |
|                                                                                                  |
|       Starts single process for the specified cluster.                                           |
|                                                                                                  |
|       Valid options:                                                                             |
|       --added|-a           Start processes added to existing cluster.                            |
|       --background|-B      Run command in background, and return prompt to the user immediately. |
|       --force|-f           Force command to completion. Bypasses sanity checks.                  |
|       --initial|-i         Use option --initial when starting.                                   |
+--------------------------------------------------------------------------------------------------+

The processid parameter should be shown as optional, and the statement "Starts single process" is not accurate as it can start multiple processes.

For example, if I've added to new data nodes to a running Cluster then running the following command will start both of those processes:

mcm> start process -a mycluster;

How to repeat:
mcm> start process --help

Suggested fix:
Update the help text to fully explain how the command can be used with the -a option to start all unstarted processes in the Cluster.