[FIXED] When calculating limits exceeded, treat replicated tier limits as flat #4868
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
… respect to limits. We had an issue with tiered accounts, where limits are flat based on type of storage. Meaning 100GB on R3 means 100GB of R3 storage, or 300GB in total. If we have limits only on an empty string tier, then consider limit as flat, otherwise scale by tier replication. Signed-off-by: Derek Collison <[email protected]>
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.
We had an issue with tiered accounts, where limits are flat based on type of storage. Meaning 100GB on R3 means 100GB of R3 storage, or 300GB in total. If we have limits only on an empty string tier, then consider limit as absolute, otherwise scale by tier replication.
Resolves issues with NGS account for HA / R3 limits.
Signed-off-by: Derek Collison [email protected]