Clarify how to monitor Aurora cluster with multiple readers #284
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Maybe it's only me with my weird reading, but when you say "If you have multiple readers you want to monitor, do X", I feel like "well I don't need to monitor them all, let me skip reading/doing X" even though I have multiple readers with a cluster.
Actually, I was always wondering what these sentences actually means, and I didn't fully understand this until today. So I think it's the best to remove any ambiguity and clarify that monitoring them individually is necessary (IOW, using for Aurora cluster with multiple readers.
Actually, just noticed that EC2 doc does say "this is only supported in two-node clusters (i.e. single reader instance)" for
cluster-roway, which is really clear. We could adopt this to other docs too 🤔