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

Add-DbaAgDatabase - Fix stale cache issue #9101

Merged
merged 3 commits into from
Oct 3, 2023
Merged

Conversation

andreasjordan
Copy link
Contributor

Fix for #9094. Reverts changes and implements the fix with just one line of code.

@potatoqualitee
Copy link
Member

@jpomfret I thought I disabled replication3. Can you check in dev why they're failing? Maybe it's just too flaky on GH actions?

@andreasjordan -- in the previous PR, it said "# calling AvailabilityDatabases.Refresh() alone is not enough". @agowa can you explain more?

@potatoqualitee
Copy link
Member

will merge this one since there was a breaking change previously and then we can address as needed. apologies i didnt notice before.

@potatoqualitee potatoqualitee merged commit 5d27f60 into development Oct 3, 2023
12 checks passed
@potatoqualitee potatoqualitee deleted the Fix_for_9094 branch October 3, 2023 13:13
@agowa
Copy link
Contributor

agowa commented Oct 3, 2023

@potatoqualitee I tried it with a local development setup of three SQL servers with one Availability group. When I just called AvailabilityDatabases.Refresh() it didn't show the current state, just the same outdated information as before. But after I ran AvailabilityReplicas.Refresh() first it correctly reflected the current state.

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.

3 participants