By using AWS re:Post, you agree to the Terms of Use
/Amazon RDS on VMWare/

Questions tagged with Amazon RDS on VMWare

Sort by most recent
  • 1
  • 90 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

RDS - Unable to change Parameter groups for Mariadb v.10.4

Hi, According to [MariaDB docs](https://mariadb.com/kb/en/optimizer-switch/), i should be able to change every possible option on or off. When i try to switch value for optimizer_switch `rowid_filter=off` in Amazon RDS -> Parameter groups, i got an error like below: > Error saving: Invalid parameter value: rowid_filter=off for: optimizer_switch allowed values are: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on (Service: AmazonRDS; Status Code: 400; Error Code: InvalidParameterValue; Request ID: 5f849923-efbc-4edc-822d-8648a0f86b9b; Proxy: null) * Pasting whole config value with `rowid_filter=off` throws the same error. * Pasting whole config value without `rowid_filter` turn on that feature - because of defaults like mentioned in docs above * Putting only value `rowid_filter=off` throws error * Engine version: 10.4.24 How can i turn one specific option off?
1
answers
0
votes
18
views
asked 6 days ago

My Postgres RDS Database is constantly reastarting suddenly due to heavyconsumption of memory. Not sure why it is happening suddenly.

My Postgres RDS Database is constantly reastarting suddenly due to heavyconsumption of memory. Not sure why it is happening suddenly. please help . some times freeable memory goes up to 30gb and suddenly comes to 8gb. not sure why. Below are logs `The database process was killed by the OS due to excessive memory consumption. It is recommended to tune your database workload and/or parameter usage to reduce memory consumption.` ``` 2022-03-07 12:17:57.302 GMT [9230] LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf" 2022-03-07 12:17:57.302 GMT [9230] LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf" 2022-03-07 12:17:57.302 GMT [9230] LOG: skipping missing configuration file "/rdsdbdata/db/postgresql.auto.conf" 2022-03-07 12:17:57 UTC::@:[9230]:WARNING: unrecognized configuration parameter "rds.adaptive_autovacuum" 2022-03-07 12:17:57 UTC::@:[9230]:WARNING: unrecognized configuration parameter "rds.enable_plan_management" 2022-03-07 12:17:57 UTC::@:[9230]:LOG: database system is shut down Postgres Shared Memory Value: 23067312128 bytes 2022-03-07 12:17:59.685 GMT [9858] LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf" 2022-03-07 12:17:59.686 GMT [9858] LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf" 2022-03-07 12:17:59.686 GMT [9858] LOG: skipping missing configuration file "/rdsdbdata/db/postgresql.auto.conf" 2022-03-07 12:17:59 UTC::@:[9858]:WARNING: unrecognized configuration parameter "rds.adaptive_autovacuum" 2022-03-07 12:17:59 UTC::@:[9858]:WARNING: unrecognized configuration parameter "rds.enable_plan_management" 2022-03-07 12:17:59 UTC::@:[9858]:LOG: starting PostgreSQL 12.4 on aarch64-unknown-linux-gnu, compiled by aarch64-unknown-linux-gnu-gcc (GCC) 7.4.0, 64-bit 2022-03-07 12:17:59 UTC::@:[9858]:LOG: listening on IPv4 address "0.0.0.0", port 5434 2022-03-07 12:17:59 UTC::@:[9858]:LOG: listening on IPv6 address "::", port 5434 2022-03-07 12:17:59 UTC::@:[9858]:LOG: listening on Unix socket "/tmp/.s.PGSQL.5434" 2022-03-07 12:17:59 UTC::@:[9858]:LOG: could not write file "pg_stat_tmp/pgss_query_texts.stat": No such file or directory 2022-03-07 12:17:59 UTC::@:[9858]:LOG: redirecting log output to logging collector process 2022-03-07 12:17:59 UTC::@:[9858]:HINT: Future log output will appear in directory "/rdsdbdata/log/error". 2022-03-07 12:20:10 UTC::@:[9859]:LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf" 2022-03-07 12:20:10 UTC::@:[9859]:LOG: skipping missing configuration file "/rdsdbdata/db/postgresql.auto.conf" 2022-03-07 12:20:30 UTC::@:[9859]:LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf" 2022-03-07 12:20:30 UTC::@:[9859]:LOG: skipping missing configuration file "/rdsdbdata/db/postgresql.auto.conf" 2022-03-07 12:26:50 UTC::@:[9859]:LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf" 2022-03-07 12:26:50 UTC::@:[9859]:LOG: skipping missing configuration file "/rdsdbdata/db/postgresql.auto.conf" 2022-03-07 13:43:53.670 GMT [22533] LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf" 2022-03-07 13:43:53.670 GMT [22533] LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf" 2022-03-07 13:43:53.670 GMT [22533] LOG: skipping missing configuration file "/rdsdbdata/db/postgresql.auto.conf" 2022-03-07 13:43:53 UTC::@:[22533]:WARNING: unrecognized configuration parameter "rds.adaptive_autovacuum" 2022-03-07 13:43:53 UTC::@:[22533]:WARNING: unrecognized configuration parameter "rds.enable_plan_management" 2022-03-07 13:43:53 UTC::@:[22533]:LOG: database system is shut down Postgres Shared Memory Value: 23067312128 bytes 2022-03-07 13:43:54.922 GMT [22660] LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf" 2022-03-07 13:43:54.922 GMT [22660] LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf" 2022-03-07 13:43:54.922 GMT [22660] LOG: skipping missing configuration file "/rdsdbdata/db/postgresql.auto.conf" 2022-03-07 13:43:54 UTC::@:[22660]:WARNING: unrecognized configuration parameter "rds.adaptive_autovacuum" 2022-03-07 13:43:54 UTC::@:[22660]:WARNING: unrecognized configuration parameter "rds.enable_plan_management" 2022-03-07 13:43:54 UTC::@:[22660]:LOG: starting PostgreSQL 12.4 on aarch64-unknown-linux-gnu, compiled by aarch64-unknown-linux-gnu-gcc (GCC) 7.4.0, 64-bit 2022-03-07 13:43:54 UTC::@:[22660]:LOG: listening on IPv4 address "0.0.0.0", port 5434 2022-03-07 13:43:54 UTC::@:[22660]:LOG: listening on IPv6 address "::", port 5434 2022-03-07 13:43:54 UTC::@:[22660]:LOG: listening on Unix socket "/tmp/.s.PGSQL.5434" 2022-03-07 13:43:55 UTC::@:[22660]:LOG: redirecting log output to logging collector process 2022-03-07 13:43:55 UTC::@:[22660]:HINT: Future log output will appear in directory "/rdsdbdata/log/error". 2022-03-07 13:45:11 UTC::@:[22732]:LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf" 2022-03-07 13:45:11 UTC::@:[22732]:LOG: skipping missing configuration file "/rdsdbdata/db/postgresql.auto.conf" 2022-03-07 13:45:30 UTC::@:[22732]:LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf" 2022-03-07 13:45:30 UTC::@:[22732]:LOG: skipping missing configuration file "/rdsdbdata/db/postgresql.auto.conf" 2022-03-07 13:49:25.588 GMT [8568] LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf" 2022-03-07 13:49:25.588 GMT [8568] LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf" 2022-03-07 13:49:25.590 GMT [8568] LOG: skipping missing configuration file "/rdsdbdata/db/postgresql.auto.conf" 2022-03-07 13:49:25 UTC::@:[8568]:WARNING: unrecognized configuration parameter "rds.adaptive_autovacuum" 2022-03-07 13:49:25 UTC::@:[8568]:WARNING: unrecognized configuration parameter "rds.enable_plan_management" 2022-03-07 13:49:25 UTC::@:[8568]:LOG: database system is shut down Postgres Shared Memory Value: 23067312128 bytes 2022-03-07 13:49:26.803 GMT [8674] LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf" 2022-03-07 13:49:26.803 GMT [8674] LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf" 2022-03-07 13:49:26.803 GMT [8674] LOG: skipping missing configuration file "/rdsdbdata/db/postgresql.auto.conf" 2022-03-07 13:49:26 UTC::@:[8674]:WARNING: unrecognized configuration parameter "rds.adaptive_autovacuum" 2022-03-07 13:49:26 UTC::@:[8674]:WARNING: unrecognized configuration parameter "rds.enable_plan_management" 2022-03-07 13:49:26 UTC::@:[8674]:LOG: starting PostgreSQL 12.4 on aarch64-unknown-linux-gnu, compiled by aarch64-unknown-linux-gnu-gcc (GCC) 7.4.0, 64-bit 2022-03-07 13:49:26 UTC::@:[8674]:LOG: listening on IPv4 address "0.0.0.0", port 5434 2022-03-07 13:49:26 UTC::@:[8674]:LOG: listening on IPv6 address "::", port 5434 2022-03-07 13:49:26 UTC::@:[8674]:LOG: listening on Unix socket "/tmp/.s.PGSQL.5434" 2022-03-07 13:49:26 UTC::@:[8674]:LOG: redirecting log output to logging collector process 2022-03-07 13:49:26 UTC::@:[8674]:HINT: Future log output will appear in directory "/rdsdbdata/log/error". ----------------------- END OF LOG ---------------------- ```
1
answers
0
votes
93
views
asked 2 months ago

Connecting RDS to an external server for replication issues

Hi all, We're going to be moving to AWS soon, and I am wanting to setup replication to an external main server . I have followed this guide: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.Procedural.Importing.External.Repl.html Steps I took: Made a user on the Main server mocking what was in the write-up I flushed privileges' I then set the main server on our AWS database CALL mysql.rds_set_external server ('XX.XX.XX.XX', 3528, 'repl_user', 'MYSQL_PASSWORD_Main', 'mysql-bin-changelog.008401', 14545731, 0); I am presented with the errors below. The MySQL port is not 3528 and not the default 3306 and although I set it differently it seems its trying to connect to that port still. Just a note we have this server replicating to another dedicated server as well so replication is working on the machine. 2021-12-13 18:30:00 2889 [Note] Error reading relay log event: SQL thread was killed 2021-12-13 18:30:00 2889 [Note] SQL thread exiting, replication stopped in log 'mysql-bin-changelog.008386' at position 53651981 2021-12-13 18:30:00 2889 [Note] was XX.XX.XX.XX:3306 2021-12-13 18:30:00 2888 [ERROR] I/O: error connecting to 'repl_user@XX.XX.XX.XX:3306' - retry-time: 60 maximum-retries: 86400 message: Can't connect to server on 'XX.XX.XX.XX' (4 "Interrupted system call"), Internal MariaDB error code: 2003 2021-12-13 18:30:00 2888 [Note] I/O thread killed while connecting to 2021-12-13 18:30:00 2888 [Note] I/O thread exiting, read up to log 'mysql-bin-changelog.008386', position 53651981 2021-12-13 18:30:00 2888 [Note] was XX.XX.XX.XX:3306 ----------------------- END OF LOG ---------------------- Any other things someone could suggest please?
1
answers
0
votes
12
views
asked 5 months ago
  • 1
  • 90 / page