NetAppDocs
Epsilon move after removing Master Node from Cluster
Page URL
https://docs.netapp.com/us-en/ontap/system-admin/remove-nodes-cluster-concept.html
Page title
Remove nodes from an ONTAP cluster
Summary
in step 3. it is mentioned to move Epsilon in case a Node that is going to be unjoined has it. in step 5. the eligibility is set to false in case the node ist the master node
In this case a new node will be selected master and also epsilon is moved. Most of the time the new master will be the HA-Partner which will be most probably also be removed. Maybe it would be good to make a remark to check for epsilon again for the second node, since most of the time I see customers and partners just set the second node eligibility also to false and I don't know if this might lead to problems in some cases where epsilon has moved to this one too
Public issues must not contain sensitive information
- [x] This issue contains no sensitive information.
@netappmf , thanks for raising this. We'll review and track updates here.
@netappmf can you clarify where you suggest adding the note? The final step (11) in the current procedure instructs the user to repeat all preceding steps on the failover partner. If all steps are repeated, the check for epsilon and the check for master is completed on the partner. If a customer simply marks the partner as false, they have deterred from the steps outlined.
@netapp-aherbin you are correct that the final step instructs the users to do it, however I've seen instance where after setting the eligibility of first node to false and seeing that now the HA-partner is the new master they will also set this to false because it will also be removed so that the master is on a different HA-pair before removing both nodes. In this case a warning in step 5a like "if you also set the eligibility of the second node to false in this step you'll have to check for epsilon again after setting it to false for the first one".
But if this will make it sound more complicated just leave it as it is, I don't now if something bad will happen when you set the eligibility to false of a node that has epsilon or if ONTAP will check this and move it before.
Best Regards Marco
@netappmf thanks! I just wanted to make sure I wasn't misunderstanding the process. We definitely want to do whatever we can to ensure customer success the first time. I'm adding the following note to step 5 for clarification.
NOTE: If you are performing this step on the first node in an HA pair, you should mark only that node as ineligible. Do not modify the status of the HA partner. If the partner node was selected as the new master, you need to verify if it holds epsilon before making it ineligible. This is done when you repeat these steps to remove the partner node.
Sounds good?
The update is posted. Thanks for helping us provide greater clarity in this procedure.