Conversation
| <itemizedlist> | ||
| <listitem> | ||
| <para> | ||
| The <literal>mysql</literal> roles are in high availability mode by setting |
There was a problem hiding this comment.
Slight change in wording - "The mysql roles can be configured to run in high availability mode..."
There was a problem hiding this comment.
Wouldn't the suggested wording not really fit the context here since we're trying say something like
If your current setup is A, go to link X
If your current setup is B, go to link Y
There was a problem hiding this comment.
I don't feel strongly about it so feel free to disregard...just sounds like something's missing. Would "The mysql roles are running in high availability mode..." sound better?
There was a problem hiding this comment.
Updated to use "are currently running in high availability mode"
| <listitem> | ||
| <para> | ||
| The <literal>mysql</literal> roles are in high availability mode by | ||
| configuring custom sizing values, see |
| <para> | ||
| For the <literal>uaa</literal> deployment, scale the instance count of the | ||
| <literal>mysql</literal> role to 1 and remove the associated persistent | ||
| volume claim. |
There was a problem hiding this comment.
We should make it clear that the PVCs corresponding to the removed instances need to be deleted, not the remaining PVC, i.e., after scaling down to mysql-0, mysql-pvc-1 and mysql-pvc-2 should be deleted.
There was a problem hiding this comment.
Update wording for this and other similar occurrences in bb88210
| from the <literal>uaa</literal> namespace. <emphasis>Do not</emphasis> | ||
| delete the persistent volume (PV). | ||
| </para> | ||
| <screen>&prompt.user;kubectl delete persistentvolumeclaim --namespace uaa mysql-data-mysql-1</screen> |
There was a problem hiding this comment.
This assumes there were only 2 instances of mysql to begin with? I think config.HA setting defaults the mysql count to 3.
There was a problem hiding this comment.
Update wording for this and other similar occurrences in bb88210
| <para> | ||
| For the <literal>scf</literal> deployment, scale the instance count of the | ||
| <literal>mysql</literal> role to 1 and remove the associated | ||
| persistent volume claim. |
There was a problem hiding this comment.
Same as above, i.e. clarify the orphaned PVCs need to be removed.
| <step> | ||
| <para> | ||
| Delete the persistent volume claim (PVC) for <literal>mysql-1</literal> | ||
| from the <literal>scf</literal> namespace. <emphasis>Do not</emphasis> |
| <para> | ||
| For the <literal>uaa</literal> deployment, scale the instance count of the | ||
| <literal>mysql</literal> role to 1 and remove the associated persistent | ||
| volume claim. |
| <step> | ||
| <para> | ||
| Delete the persistent volume claim (PVC) for <literal>mysql-1</literal> | ||
| from the <literal>uaa</literal> namespace. <emphasis>Do not</emphasis> |
There was a problem hiding this comment.
In this case the customer would need to delete all the orphaned PVCs for the rest of the instances, not just the one corresponding to mysql-1...
| <para> | ||
| For the <literal>scf</literal> deployment, scale the instance count of the | ||
| <literal>mysql</literal> role to 1 and remove the associated | ||
| persistent volume claim. |
| <step> | ||
| <para> | ||
| Delete the persistent volume claim (PVC) for <literal>mysql-1</literal> | ||
| from the <literal>scf</literal> namespace. <emphasis>Do not</emphasis> |
4 participants
No description provided.