-
Notifications
You must be signed in to change notification settings - Fork 268
unable to set some parameters in the DbClusterParameterGroup #1847
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @luis-alen , the rds-controller uses a kinda specific cache implementation inside the controller. Can you try to restart the controller? if the problem is solved them we might have an issue with the cache implementation :) |
Hey, @a-hilaly. Unfortunately it didn't help. I turned on debug log level for the controller and I see that it captures the change, but is unable to apply it.
|
@a-hilaly I also verified the same with debug logs, and see that DbClusterParameterGroup object goes into not synced mode and throws an error 'unknown parameter: long_query_time', We also see the error on the |
Also, Debug logs don't show much information other than what is mentioned in the #1847 (comment) |
@a-hilaly further investigating the issue: the error is only coming for the parameters which are https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.ParameterGroups.html#AuroraMySQL.Reference.Parameters.Instance instance level. However, I need to check how the status is updated on DBClusterParameterGroup since it shows Instance instance level parameters in the status section. |
We're using controller version 1.1.10. We just encountered this with - message: 'unknown parameter: idle_in_transaction_session_timeout'
status: 'True'
type: ACK.Terminal I removed this parameter from the spec, and restarted the controller, but the error still persists. |
@cogren1 aws-controllers-k8s/rds-controller#167 will fix the issue that you are facing. However please make sure, DbClusterParameterGroup should have Cluster Level Parameters https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.ParameterGroups.html#AuroraMySQL.Reference.Parameters.Instance |
@riddhi2910 Thank you for linking that fix. I look forward to it getting in! idle_in_transaction_session_timeout is a parameter that exists in cluster parameter groups for Aurora Postgres. |
@cogren1 Yeah that isn't very clear, the console UI can do much more than the API call to fetch the supported cluster-level parameters. |
Hello, I am experiencing the same problem, any solutions?
|
Issues go stale after 180d of inactivity. |
We're also having this issue. When should you use In any case, I'm trying to set e.g. |
/remove-lifecycle stale |
Describe the bug
I'm unable to set parameters such as
slow_query_log
,long_query_time
andlog_queries_not_using_indexes
inDbClusterParameterGroup
objects. I get anunknown parameter
error message:I'm able to set parameters such as
character_set_*
, but the not the ones I mentioned above. I confirm that such parameters are available and are modifiable on the db cluster parameter group using the aws console.I also confirm that it does work for the
DbInstance
kind. Maybe it's somehow related to #869 (comment)?Steps to reproduce
Try to create a new
DbClusterParameterGroup
or try updating an existing one (with family aurora-mysql8.0) overwriting theslow_query_log
parameter.Expected outcome
Parameter should be set accordingly.
Environment
The text was updated successfully, but these errors were encountered: