Which solution will meet these requirements?
Modify the rds.log_retention_period parameter to 0. Reboot the DB instance to save the changes.
Modify the rds.log_retention_period parameter to 1440. Wait up to 24 hours for database logs to be deleted.
Modify the temp_file_limit parameter to a smaller value to reclaim space on the DB instance.
Modify the rds.log_retention_period parameter to 1440. Reboot the DB instance to save the changes.
Explanations:
Modifying therds.log_retention_periodparameter to 0 would delete logs, but this change requires a DB instance reboot, which would result in downtime. The requirement specifies no downtime.
Modifying therds.log_retention_periodparameter to 1440 (24 hours) allows logs to be deleted after a period, freeing up space. This change does not require a reboot and does not result in downtime.
Modifying thetemp_file_limitparameter impacts temporary file usage, but it doesn’t directly address reclaiming storage used by database logs. This change wouldn’t help recover the consumed storage from the logs.
Modifying therds.log_retention_periodparameter to 1440 and rebooting the instance would cause downtime, which violates the requirement for no downtime. The log retention change can occur without a reboot.
I sort that the answer is:
Modify the rds.log_retention_period parameter to 1440. Wait up to 24 hours for database logs to be deleted.
If I’m correct, the answer is:
Modify the rds.log_retention_period parameter to 1440. Wait up to 24 hours for database logs to be deleted.