Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NetApp replica promote: guard source being down #141

Draft
wants to merge 2 commits into
base: stable/xena-m3
Choose a base branch
from

Conversation

Carthaca
Copy link
Collaborator

Constructing a vserver client to the old active replica
may fail in a disaster scenario. Promoting the non-active
replica must work nevertheless.

Change-Id: Ib1a36f45ba47e378e13acd24ea16634ed96e15ca

Constructing a vserver client to the old active replica
may fail in a disaster scenario. Promoting the non-active
replica must work nevertheless.

Change-Id: Ib1a36f45ba47e378e13acd24ea16634ed96e15ca
LOG.exception(msg, replica['id'])
return replica
except netapp_api.NaApiError:
# Catch everything! The original source may be down,
Copy link
Member

@chuan137 chuan137 Oct 24, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am wondering is such a disaster situation, there is better way to handle it than error it out. Can we forcefully cut the old snapmirror relationships and elect the new replica? It might be helpful when there are more than two replicas

maybe we can drill down into the change_snapmirror_source() method
maybe add a comment for later to improve

The 'aborting' takes a while until snapmirror break can continue,
give it 2 minutes at most.

Change-Id: I0b411a00ab1fd72756e60e64cd9a71482a7998be
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants