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

Remove isMultiWriterCluster flag and ignore stale records when querying the topology #435

Merged
merged 2 commits into from
May 11, 2023

Conversation

crystall-bitquill
Copy link
Contributor

Summary

Remove the isMultiWriterCluster flag from the AuroraTopologyService and add checks for stale topology records.

Description

Multi writer clusters are not longer supported, so the isMultiWriterCluster flag that was used to disable failover has been removed. Additionally, checks have been added to ensure stale writer records that are obtained post writer-failover are not being used.

Additional Reviewers

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@@ -39,6 +42,8 @@ public class HostSpec {
protected Set<String> allAliases = ConcurrentHashMap.newKeySet();
protected long weight; // Greater or equal 0. Lesser the weight, the healthier node.
protected String hostId;
protected String lastUpdateTime;
Copy link
Contributor

@sergiyvamz sergiyvamz May 10, 2023

Choose a reason for hiding this comment

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

Can we use date/timestamp object instead of String?

@sergiyvamz sergiyvamz merged commit 8804836 into aws:main May 11, 2023
@crystall-bitquill crystall-bitquill deleted the remove-isMultiWriterCluster branch May 11, 2023 22:36
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