英文:
AWS Neptune - How Can I Migrate My 1.0.5.1 Based Cluster to Serverless?
问题
我有一个 Amazon Neptune 集群，其中有一个运行在 db.t3.medium 数据库实例类型上的实例。我没有看到将其迁移到无服务器实例的选项。
我该如何迁移这个实例？
英文:
The Problem
I have an Amazon Neptune cluster with an instance running in db.t3.medium DB instnance class. I do not see a choice to move this to the Serverless instance.
How can I migrate this instance?
答案1
得分: 1
根本原因
只能迁移运行 Neptune 引擎版本 1.2 或更高版本的实例。
如何修复
首先需要将 Neptune 引擎版本迁移至 1.2。完成后，您将获得迁移选项到无服务器。
引擎版本不是在集群实例级别控制的，而是在集群级别控制的。如果您运行的是旧版本的引擎，您可能需要逐步升级到主要版本组中最高版本，然后升级到更高版本。如果您运行的是 1.0.x 版本，首先需要升级到 1.1.0 R7，然后再升级到 1.2。
与任何主要版本升级一样，迁移过程中可能会出现一些停机时间。
要更改引擎版本，请在集群（而非实例）设置中点击“修改”（控制台页面右上角的按钮），然后选择最新可能的 DB 引擎版本。您可以保留其余设置，并且如果您可以在稍后立即启动停机时间，可以应用更改以立即生效。继续升级到下一个更高级别，直到达到 1.2。每次升级可能需要一些时间。
英文:
Root Cause
You can only migrate an instance running Neptune Engine version 1.2 or later.
How to Fix
You need to migrate your Neptune Engine version first to 1.2. Once that is done, you will get the migration option to Serverless.
The engine version is controlled not in the cluster instance but at the cluster level and if you are running an older version of the engine, you may need to incrementally upgrade to from the highest version in the major version group, then move up to the next higher version. If you are running 1.0.x, you will first need to go to 1.1.0 R7 then move onto 1.2.
As with any major version upgrade, you could incur some downtime during migration.
To change the engine version, "Modify" the cluster (not instance) settings (the top right button on the console page) and select the latest possible DB engine version. You can keep the rest of the settings, and you can apply the change to take effect immediately if you can afford to initiate a downtime shortly after. Continue to upgrade to the next higher level until you reach 1.2. Each upgrade can take a while.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论