Changes to server_collation on aurora mysql8 instance is not applied

0

Hi

When changing collation_server on a 8.0.mysql_aurora.3.01.0 DB cluster it seems like the change is not applied to existing clusters but only new ones.

A custom DB cluster parameter group was created with collation_server=utf8_bin and a cluster was created using it. Later we changed to collation_server=utf8mb4_bin but the cluster now reports collation_server=utf8mb4_0900_ai_ci when executing show variables like 'c%_server' (also confirmed that when you run create database test it gets the wrong collation).

It seems like it is only related to collation_server, the value of character_set_database seems to get applied correctly.

If I create a new cluster using the updated parameter group it works as expected

Can anyone reproduce / confirm this?

Best regards Jens

profile picture
jtm
질문됨 2년 전1107회 조회
1개 답변
0
수락된 답변

Check reboot pending status.

If a DB instance isn't using the latest changes to its associated DB parameter group, the AWS Management Console shows the DB parameter group with a status of pending-reboot. The pending-reboot parameter groups status doesn't result in an automatic reboot during the next maintenance window. To apply the latest parameter changes to that DB instance, manually reboot the DB instance.

https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithParamGroups.html

답변함 2년 전
  • I can confirm that rebooting resolves the issue, thanks.

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠