By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Aurora reader creation dialog doesn't offer instance type options

0

I'm trying to create a new aurora reader for an existing aurora cluster with an existing writer instance. When I use the Add Reader option from the console the DB instance class drop-down is empty and so I can't proceed. I tried this same thing last week (in a test run) without issue. This occurs both for a newly created cluster and long running cluster. Both clusters are 5.6.mysql_aurora.1.22.3 . Looking at the developer's console in my browser (while on the Add Reader screen)I see the following errors: Uncaught TypeError: Cannot read properties of null (reading 'DBInstanceIdentifier') at t.onCreateReadReplicaClicked (chunk884.js:1:185106) at t.handleItemClick (chunk884.js:1:160188) at HTMLElement.wrappedCallback (chunk5982.js:2:2265773) at a (chunk5982.js:2:2230014) at e.__fireEvent (chunk5982.js:2:2230474) at Object.__activateItem (chunk5982.js:2:2274620) at HTMLLIElement.m (chunk5982.js:2:2301008)

and a little later rds-0.js:16386 Wed Oct 19 21:03:05 GMT-500 2022 SEVERE: Uncaught Client Exception: com.google.web.bindery.event.shared.UmbrellaException: Exception caught: Exception caught: Cannot find version 5.6.mysql_aurora.1.22.3 for aurora (Service: AmazonRDS; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: 7d821db1-b674-430a-a24c-bf683ff28a17; Proxy: null) at Unknown.google.web.bindery.event.shared.UmbrellaException: Exception caught: Exception caught: Cannot find version 5.6.mysql_aurora.1.22.3 for aurora(Service: AmazonRDS; Status Code: 400; Error Code: InvalidParameterCombination; Request ID) Caused by: com.google.web.bindery.event.shared.UmbrellaException: Exception caught: Cannot find version 5.6.mysql_aurora.1.22.3 for aurora (Service: AmazonRDS; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: 7d821db1-b674-430a-a24c-bf683ff28a17; Proxy: null) at Unknown.google.web.bindery.event.shared.UmbrellaException: Exception caught: Cannot find version 5.6.mysql_aurora.1.22.3 for aurora(Service: AmazonRDS; Status Code: 400; Error Code: InvalidParameterCombination; Request ID) Caused by: java.lang.RuntimeException: Cannot find version 5.6.mysql_aurora.1.22.3 for aurora (Service: AmazonRDS; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: 7d821db1-b674-430a-a24c-bf683ff28a17; Proxy: null) at Unknown.lang.RuntimeException: Cannot find version 5.6.mysql_aurora.1.22.3 for aurora(Service: AmazonRDS; Status Code: 400; Error Code: InvalidParameterCombination; Request ID)

This seems to be a new error in the behavior of the Add Reader screen. Any advice?

  • rePost-User-0266921
    a year ago

    FWIW I also see similar javascript errors and an empty DB instance class select menu, when just selecting an existing aurora mysql instance and clicking the modify button. I was able to create a reader instance from the CLI. So this seem to be an issue with the RDS console itself and not the underlying aurora functionality.

Topics
DatabaseAnalytics
Tags
DatabaseAmazon AuroraAurora MySQL
Language
English
rePost-User-0266921
asked a year ago428 views
2 Answers
1

It seems RDS console issue with the version which is no longer able to launch new Aurora MySQL cluster(e.g. Aurora MySQL version1). Please try with AWS CLI to add new Reader instance

aws rds create-db-instance --db-instance-identifier READER_INSTANCE_IDENTIFIER --db-cluster-identifier DB_CLUSTER_IDENTIFIER --engine aurora --db-instance-class DB_INSTANCE_TYPE --region YOUR_REGION

https://awscli.amazonaws.com/v2/documentation/api/latest/reference/rds/create-db-instance.html

AWS
YUTAKA_H
answered a year ago
  • rePost-User-0266921
    a year ago

    Yes, I was able to add a reader via the CLI. So I agree, it appears to be a console issue.

  • Indranil Banerjee AWS EXPERT
    a year ago

    No I was not able to reproduce on the console. You must have run into some sort of boundary condition which cannot be debugged without looking at logs or without having a clearly reproducible set of steps. I agree, the Aurora service team should fix an issue. The only thing I was trying to point out is I am not aware of a mechanism other than through support to bring the issue to the attention of the service team. Will try to find out internally.

  • Indranil Banerjee AWS EXPERT
    a year ago

    OK. Yutaka informed me that this issue is reproducible only with older versions of MySQL and is a known issue and a ticket has been opened internally for it. Thanks Yutaka.

0

In which region is this? I could not reproduce the issue in us-west-2 region. You will need to open a Support case so Customer Support can take a look at what the issue is.

profile pictureAWS
EXPERT
Indranil Banerjee AWS
answered a year ago
  • rePost-User-0266921
    a year ago

    This is in us-east-1. I'm not on a paid support plan so I can't open a ticket. The javascript error is getting thrown by js running as part of the RDS console. Presumably that's something the RDS team would be interested in knowing about and fixing regardless of whether I happen to be paying extra for support or not.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content