MySQL InnoDB Cluster - Revision history

Michael.mast: /* Restart from full shutdown */

2021-06-29T10:56:13Z

Restart from full shutdown

2021-06-29T02:49:20Z

Restart from full shutdown

2021-06-29T02:47:09Z

Restart from full shutdown

2021-06-28T12:41:22Z

Restart from full shutdown

2021-06-28T12:26:55Z

Restart from full shutdown

2021-06-28T12:26:47Z

Restart from full shutdown

2021-06-28T12:10:37Z

Troubleshooting

2021-06-08T18:46:14Z

Troubleshooting

2021-06-08T17:31:33Z

Troubleshooting

2021-06-08T17:25:07Z

Troubleshooting

@@ Line 147: / Line 147: @@
 Dba.rebootClusterFromCompleteOutage: The active session instance (mysql02:3306) isn't the most updated in comparison with the ONLINE instances of the Cluster's metadata. Please use the most up to date instance: 'mysql01:3306'. (RuntimeError)
 </pre>
-*Switched to node1 and re-ran. It took a while on the old Xeon cores I was working with.
+*Switched to node1 and re-ran, however I received an error stating that the plugin timed out waiting for the super read only to be removed. I ended up
 <ref>https://books.google.com/books?id=11ptDwAAQBAJ&pg=PA110&lpg=PA110&dq=mysql+innodb+cluster+super+read+only+time+out&source=bl&ots=wNWazQsNfj&sig=ACfU3U2zDAiqbsZboDVbMgrs96Bc2_bt-Q&hl=en&sa=X&ved=2ahUKEwiPk7C94rvxAhXLQc0KHelXAEcQ6AEwCXoECAsQAw#v=onepage&q=mysql%20innodb%20cluster%20super%20read%20only%20time%20out&f=false</ref><pre>
 select member_host,member_role from performance_schema.replication_group_members;
 </pre>

@@ Line 137: / Line 137: @@
 </pre>
 ===Restart from full shutdown===
-<ref>https://dba.stackexchange.com/questions/195853/dba-getcluster-this-function-is-not-available-through-a-session-to-a-standalone</pre>
+<ref>https://dba.stackexchange.com/questions/195853/dba-getcluster-this-function-is-not-available-through-a-session-to-a-standalone</ref></pre>
 *Log into node with cluster admin privileges.
 <pre>

← Older revision		Revision as of 02:47, 29 June 2021
Line 148:		Line 148:
	</pre>		</pre>
	*Switched to node1 and re-ran. It took a while on the old Xeon cores I was working with.		*Switched to node1 and re-ran. It took a while on the old Xeon cores I was working with.
		+	<ref>https://books.google.com/books?id=11ptDwAAQBAJ&pg=PA110&lpg=PA110&dq=mysql+innodb+cluster+super+read+only+time+out&source=bl&ots=wNWazQsNfj&sig=ACfU3U2zDAiqbsZboDVbMgrs96Bc2_bt-Q&hl=en&sa=X&ved=2ahUKEwiPk7C94rvxAhXLQc0KHelXAEcQ6AEwCXoECAsQAw#v=onepage&q=mysql%20innodb%20cluster%20super%20read%20only%20time%20out&f=false</ref><pre>
		+	select member_host,member_role from performance_schema.replication_group_members;
		+	</pre>

@@ Line 138: / Line 138: @@
 ===Restart from full shutdown===
 <ref>https://dba.stackexchange.com/questions/195853/dba-getcluster-this-function-is-not-available-through-a-session-to-a-standalone</pre>
 <pre>
 mysqlsh -u<cluster admin> -p
 cluster = dba.rebootClusterFromCompleteOutage()
 </pre>

@@ Line 140: / Line 140: @@
 <pre>
 mysqlsh -u<cluster admin> -p
-dba.rebootClusterFromCompleteOutage()
+cluster = dba.rebootClusterFromCompleteOutage()
 </pre>

@@ Line 135: / Line 135: @@
 set global super_read_only = 0;
 set global read_only = 0;
 </pre>

@@ Line 121: / Line 121: @@
 </pre>
 From a complete split brain issue I ran into:
 *Connect to whichever node is working, then force it as primar.
 <pre>
@@ Line 130: / Line 131: @@
 dba.dropMetadataSchema()
 </pre>
-*However, I also needed to remove super read only manually. Drop out of shell and run the following via mysql
+*This was not needed, but is good to know.
 <pre>
 set global super_read_only = 0;
 set global read_only = 0;
 </pre>

@@ Line 120: / Line 120: @@
 cluster.setPrimaryInstance("mysql01.domain.net")
 </pre>
-From a complete split brain issue I ran into
+From a complete split brain issue I ran into:
 <pre>
 cluster.forceQuorumUsingPartitionOf("root@mysql01.domain.net")
 </pre>