Bug #83623 Rename --initial-start option to --partial-start
Submitted: 31 Oct 2016 20:11 Modified: 1 Nov 2016 11:51
Reporter: Jon Stephens Email Updates:
Status: Verified Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:7.2+ OS:Any
Assigned to: CPU Architecture:Any

[31 Oct 2016 20:11] Jon Stephens
NDB data node processes have to similarly-named options, --initial and --initial-start.

--initial is suitably named; it is used when performing an initial start of a data node--that is, when doing a clean start that wipes all cluster data.

The --initial-start option, which is used when performing a partial start of the cluster, is very badly named, since it does *not* (to my knowledge, at least) clear the node filesystem.

We should *avoid* using anything that sounds like "initial start" for anything other than an actual initial start that wipes the cluster's data. We *should* use "partial start"/--partial-start for a partial start of the cluster, since this is what it is.

How to repeat:
See above.

Suggested fix:
1. Rename the data node option from --initial-start to --partial-start.

2. Update documentation to replace references to "partial initial start" with "partial start"; calling it "initial" is erroneous and confusing.