-
Notifications
You must be signed in to change notification settings - Fork 43
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
RDS Modules Bumping - Large Storage Size DB Approach #6370
Comments
The below output is as of Oct 24 20:00, removed the email address in
|
The below output is as of Oct 24 20:00, removed the email address in
|
timckt
changed the title
RDS Modules Bumping - Large Storage Size DB Approach
RDS Modules Bumping - Approach Large Storage Size DB
Oct 24, 2024
timckt
changed the title
RDS Modules Bumping - Approach Large Storage Size DB
RDS Modules Bumping - Large Storage Size DB Approach
Oct 25, 2024
|
Down to 7:
|
This ticket will be covered by #6606 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TL;DR:
When bumping module, users will need to take action and set the
db_iops
value to be at least12000
for below 14 + 8 = 22 DBsFor 14 postgres/mariadb
For 8 oracle
Background
We have cut the major
8.0.0
release for RDS module and we are going to bump the modules across our platform.For all RDS DB engines except RDS for SQL Server, the baseline storage performance for gp3 volumes increases when the storage size reaches certain thresholds. This means that when user upgrade the module and switch to
gp3
, they may need to adjust thedb_iops
value accordingly to ensure optimal performance, especially for RDS instances with large volumes.gp3
Storage TypeWhen bumping module, users will need to take action and set the
db_iops
value to be at least12000
for :Db2
,MariaDB
,MySQL
,PostgreSQL
with larger than 399allocated_storage
andgp2
storage_type
(We have 14 DB as of Oct 24 20:00 in this case.)Oracle
with larger than 199allocated_storage
andgp2
storage_type
(We have 8 DB as of Oct 24 20:00 in this case.)The complete output are in below comment.
Proposed user journey
Approach
Which part of the user docs does this impact
Communicate changes
Questions / Assumptions
Definition of done
Reference
How to write good user stories
The text was updated successfully, but these errors were encountered: