| Bug #83208 | creating a cluster should ask master key twice | ||
|---|---|---|---|
| Submitted: | 29 Sep 2016 14:42 | Modified: | 11 May 2018 19:19 |
| Reporter: | Kenny Gryp | Email Updates: | |
| Status: | Won't fix | Impact on me: | |
| Category: | MySQL Server: Document Store: MySQL Shell | Severity: | S4 (Feature request) |
| Version: | 5.7.15 preview MIC | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | mic, mysql innodb cluster | ||
[3 Oct 2016 9:42]
MySQL Verification Team
Hello Kenny, Thank you for the report and feedback! Observed this while verifying Bug#83235 Thanks, Umesh
[11 May 2018 19:19]
Hema Sridharan
From development team: Hi Umesh Even your request was completely valid (and a good one) you may have noted we changed the security model, we are no longer using the Master Key approach and so this request goes obsolete. Thank you so much for your help testing the shell.

Description: When I created a cluster, I had to only enter the master key once. Now I made a typo and I don't know the key anymore. How to repeat: ``` mysql-js> cluster = dba.createCluster('plam') A new InnoDB cluster will be created on instance 'root@mysql3:3306'. When setting up a new InnoDB cluster it is required to define an administrative MASTER key for the cluster. This MASTER key needs to be re-entered when making changes to the cluster later on, e.g.adding new MySQL instances or configuring MySQL Routers. Losing this MASTER key will require the configuration of all InnoDB cluster entities to be changed. Please specify an administrative MASTER key for the cluster 'plam': Creating InnoDB cluster 'plam' on 'root@mysql3:3306'... Adding Seed Instance... Cluster successfully created. Use Cluster.addInstance() to add MySQL instances. At least 3 instances are needed for the cluster to be able to withstand up to one server failure. <Cluster:plam> mysql-js> ``` Suggested fix: It would be great if the master key is asked twice so I am less likely to make a typo as now I have to remove and recreate the cluster