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

event_scheduler is OFF in Aurora MySQL Serverless DB despite being set in the parameter group

1

We're using an aurora-mysql5.7 Serverless database, and have created a new DB cluster parameter group with event_scheduler set to ON. After switching the cluster's parameter group and confirming the cluster was rescaled in the logs, the change hasn't taken effect in MySQL.

SHOW VARIABLES LIKE "event_scheduler"; outputs OFF, and SELECT LAST_EXECUTED FROM INFORMATION_SCHEMA.EVENTS; returns null for the event I created, despite it being well over the interval.

I can't find anywhere in the documentation about this parameter not being compatible with Aurora Serverless, so not sure why this doesn't seem to be working.

1 Answers
1
Accepted Answer

Hello Bhollier,

I understand that you are trying to set the event_scheduler of your aurora-mysql5.7 serverless database to on and the change do not take effect.

Please always make sure to reboot your instance after applying the changes to your parameter groups, see reference [1] for more information on rebooting database instances.

You can also check if the specific property modification is supported by the Serverless engine or not by running this command:

aws rds describe-db-cluster-parameters --db-cluster-parameter-group-name <param-group-name>

If the parameter group is supported, the output of the command will show:

"SupportedEngineModes": [

            "provisioned",

            "serverless"

]

If you are using Aurora Serverless v2, please refer to reference [2] for the parameter groups configuration.

If you are using Aurora Serverless v1, please refer to reference [3]: (Modifying parameter values for Aurora Serverless v1) for the parameter groups configuration.

  • Please also note that unlike provisioned Aurora DB clusters, an Aurora Serverless v1 DB cluster has a single read/write DB instance that's configured with a DB cluster parameter group only—it doesn't have a separate DB parameter group. During autoscaling, Aurora Serverless v1 needs to be able to change parameters for the cluster to work best for the increased or decreased capacity. Thus, with an Aurora Serverless v1 DB cluster, some of the changes that you might make to parameters for a particular DB engine type might not apply and therefore the event_scheduler parameter may not be modifiable in Aurora Serverless. For more information on this, please refer to reference [3].

You can get a list of default values for the default parameter groups for the various Aurora DB engines by following the information on reference [4].

For more information on Aurora MySQL configuration parameters, please see reference [5].

References:

[1] https://docs.aws.amazon.com/cli/latest/reference/rds/reboot-db-instance.html

[2] https://docs.amazonaws.cn/en_us/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2.setting-capacity.html#aurora-serverless-v2.parameter-groups

[3] https://docs.amazonaws.cn/en_us/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v1.how-it-works.html

[4] https://docs.aws.amazon.com/cli/latest/reference/rds/describe-engine-default-cluster-parameters.html

[5] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.html#AuroraMySQL.Reference.Parameters.Instance

I hope this helps.

answered a month ago

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