大网数据广告活动
服务器运维问答

Why AWS RDS doesn't update minor version?

· 52CE 我爱测

I have a small RDS instance on AWS, and on the maintenance details I have set "Auto minor version upgrade" to Yes. But I still have the MySQL engine version 5.5.27, and AWS has the version 5.5.33 available. Am I missing something…

问题原文

原帖链接 · Andres · CC BY-SA 3.0

I have a small RDS instance on AWS, and on the maintenance details I have set "Auto minor version upgrade" to Yes. But I still have the MySQL engine version 5.5.27, and AWS has the version 5.5.33 available. Am I missing something here?

已采纳解答

原帖链接 · Michael - sqlbot · CC BY-SA 3.0

I have a couple of out of sight, out of mind 5.5 instances in RDS, and it turns out they are running 5.5.27 as well.

Between 5.5.27 and the highest currently-available version, 5.5.33, RDS for MySQL 5.5 only (apparently) supported one other minor release, which was 5.5.31.

RDS originally posted a schedule of when minor version upgrades to 5.5.33 would be done, and they subsequently announced they had suspended those automatic upgrades:

On 30th October 2013, based on signals we received from our monitoring systems, we paused the upgrade process in all the Regions. We will review the system and post a new schedule for the upgrades in the future.

This should explain why your system wasn't upgraded to 5.5.33, but it doesn't explain why you weren't upgraded to 5.5.31... or why I wasn't.

Then I realized that I don't actually remember an announcement about automatic upgrades to 5.5.31.

I searched for it, and didn't find it.

I did, however find the announcement of scheduled automatic upgrades to 5.5.27.

This leads me to speculate that RDS never actually did a mass upgrade to 5.5.31 like they did to 5.5.27 or will presumably still be doing to 5.5.33... in which case, the state of your instances, and my instances, makes sense. I've searched pretty diligently and come up with no other explanations. The AWS forum is also very low on search results when it comes to any questions referencing 5.5.31 at all. I have also not been able to encounter any other "unsuspected settings" that would have stopped automatic minor version upgrades.

So I don't think you're missing something, I suspect that you will be automatically upgraded to 5.5.33 when they resume the automatic upgrades. My plan is to wait, and if the upgrades roll around and I don't get mine, post to the forums.

The only other options, it seems like, would be to post to the forums now, to see if you can get an AWS person's attention or feedback from any users with suggestions... or to manually select the new minor version and apply it to your instance, though that won't serve to answer the question of whether minor version upgrades are broken, or whether what we're currently seeing is pretty much what we should be seeing, on systems running 5.5.27.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2013-11-16)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。