Questions tagged with MariaDB
Content language: English
Sort by most recent
Hi,
I want to know where does RDS store its log files.
Is it on the same storage as the database data is located?
I am asking this because we added audit logging and we expect the logs to be fairly large, will this impact performance?
Amazon RDS will start deprecating M1, M2, M3, R3, and T1 instances for your PostgreSQL, MySQL, and MariaDB databases from February 6, 2023.
All PostgreSQL, MySQL, or MariaDB databases running in Amazon RDS on M1, M2, M3, R3, or T1 instances will be automatically upgraded as per the upgrade path outlined below by RDS, no earlier than February 6, 2023 starting 12 AM UTC:
|Existing Instance | Size,Existing Specs | New Instance Size | New Instance Specs |
| --- | --- | --- | --- |
|db.m1.small | 1 vCPU, 1.70 GB | db.t3.small | 2 vCPU, 2.00 GB |
|db.m1.medium | 1 vCPU, 3.75 GB | db.t3.medium | 2 vCPU, 4.00 GB |
|db.m1.large | 2 vCPU, 7.50 GB | db.m5.large | 2 vCPU, 8.00 GB |
|db.m1.xlarge | 4 vCPU, 15.00 GB | db.m5.xlarge | 4 vCPU, 16.00 GB |
|db.m2.2xlarge | 4 vCPU, 34.20 GB | db.r5.xlarge | 4 vCPU, 32 GB |
|db.m2.4xlarge | 8 vCPU, 68.40 GB | db.r5.2xlarge | 8 vCPU, 64 GB |
|db.m3.medium | 1 vCPU, 3.75GB | db.t3.medium | 2vCPU, 4GB |
|db.m3.large | 2 vCPU, 7.5 GB | db.m5.large | 2 vCPU, 8 GB |
|db.m3.xlarge | 4 vCPU, 15GB | db.m5.xlarge | 4 vCPU, 16 GB |
|db.m3.2xlarge | 8 vCPU, 30GB | db.m5.2xlarge | 8 vCPU, 32 GB |
|db.r3.large | 2 vCPU 15.25 GB | db.r5.large | 2 vCPU, 16 GB |
|db.r3.xlarge | 4 vCPU, 30.5GB | db.r5.xlarge | 4 vCPU, 32 GB |
|db.r3.2xlarge | 8 vCPU, 61GB | db.r5.2xlarge | 8 vCPU, 64 GB |
|db.r3.4xlarge | 16 vCPU, 122GB | db.r5.4xlarge | 16 vCPU, 128 GB |
|db.r3.8xlarge | 32 vCPU, 244GB | db.r5.8xlarge | 32 vCPU, 256 GB|
Migration will be done in the maintenance window of your RDS instance. During this migration, your database may be shutdown and restarted multiple times. If you choose the “Apply Immediately” option, the migration will be initiated immediately after clicking on the “Modify DB Instance” button. If you choose not to apply the change immediately, the migration will be performed during your next maintenance window.
Your PostgreSQL, MySQL, or MariaDB databases in Amazon RDS running on M1, M2, M3, R3, or T1 instances will be automatically migrated to an equivalent M5, R5, or T3 instance by RDS, no earlier than February 6th, 2023 starting 12 AM UTC, as per the migration path.
To avoid any unplanned disruptions, we recommend that you migrate your PostgreSQL, MySQL, and MariaDB databases in Amazon RDS running on M1, M2, M3, R3, or T1 instances to an equivalent M5, R5, or T3 instance before February 3, 2023.
To learn more about the latest instance types supported on RDS, refer to the Amazon RDS user guide [1]. For guidance on modifying your instance class, see the Amazon RDS User Guide [2]. If you have any questions or concerns, the AWS Support Team is available via re:Post [3] and via AWS Premium Support [4].
[1] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.DBInstanceClass.html#Concepts.DBInstanceClass.Types
[2] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.DBInstance.Modifying.html
[3] https://repost.aws
[4] https://aws.amazon.com/support
asked 3 months ago
So I have access inside my virtual machine to run mysql with the following commands: mysql -h (IP for mariadb) -u (user) -p (password) databasename Now, when I try creating the following commands to run mariadb inside of a docker container: [ref] (how to remote access to mariadb on docker?). Then, when I do show tables it says Empty set (0.000 sec). I don't know why I am not able to see the data through docker. I tried using docker ip for the container as well and same thing as well. Does anyone know a way around this? Thank you in advance.
asked 3 months ago
Hi All,
Currently, I have a RDS instance that is sitting inside a private subnet and they are connected to EC2 [Linux Instances] that are in a public subnet.
Is there any way for the developers to access the RDS using mysql workbench? Accessing the RDS via CLI is a challenge,
Hello,
we are waiting and looking forward to MariaDB 10.7+ for RDS. I know that nobody can provide exact date but still. Can we expect it in reasonable time span?
* Version 10.7 was released on 14th Feb 2022 and it is still not available for RDS. (after 9 months)
* Version 10.6 was released on 6th Jul 2021 and it was available for RDS on 3rd Feb 2022. (after 7 months)
So it is about time for 10.7 :) . Do we have some gossip?
Plus MariaDB seems to have stopped LTS or significantly shortened its length. What are plans regarding this fact?
https://mariadb.com/kb/en/setting-up-replication/
I have used these instructions to setup 10 or so master slave replications successfully. I now want to do the same where the master is on-premise, and the slave is on an AWS EC2 RDP. The on-premise network is connected via a site-to-site VPN. Communications have been tested successfully. Can I use the same instructions above? When I look for the my.cnf file on the AWS RDP slave I cannot find it? Also when I try to use the change master to command it says I have to have "super" rights. When I try to enable super rights AWS will not allow me.
Is there a different set of instructions I should use for replicating with AWS?
Sometimes after we schedule a pending maintenance, we would want to un-schedule it because of newly discovered dependent applicative operations for that specific day, so a clear/reset apply date button would be helpful.
instead of using docker ip address of container how can app use assigned IP address of AWS Lightsail
Hi,
I have a static IP address assigned to AWS Lightsail instance. This IP Address was cleared for me to get access to MariaDB. I am now using docker for my project and docker has another IP address than that of the instance. This results in an error stating: "IPxxx" is not allowed to connect to this mariadb server. Is there anything I have to do within AWS to get this access? Thanks in advance.
asked 5 months ago
I think I discovered a bug. I tried running my Terraform code for my resources in Region Asia Pacific (Jakarta) `ap-southeast-3`.
Previously it's something like this
```
resource "aws_db_instance" "test_database" {
allocated_storage = 30
max_allocated_storage = 100
engine = "mariadb"
engine_version = "10.6.8"
```
Then the console output
```
InvalidParameterCombination: Cannot upgrade mariadb from 10.6.10 to 10.6.8
```
I tried changing to `10.6`
```
resource "aws_db_instance" "test_database" {
allocated_storage = 30
max_allocated_storage = 100
engine = "mariadb"
engine_version = "10.6"
```
It shows
```
InvalidParameterCombination: RDS does not support creating a DB instance with the following combination: DBInstanceClass=db.t3.micro, Engine=mariadb, EngineVersion=10.6.10, LicenseModel=general-public-license. For supported combinations of instance class and database engine version, see the documentation.
```
I checked in the RDS console for my instance. It's somewhat already in version `10.6.10`.
But when I tried modify the instance, the options shows nothing
Then I tried creating a new RDS, there is no options `10.6.10`.
Our RDS database has been in state 'Upgrading' for over 5 hours. It appears it was applying an `Automatic minor version upgrade to mariadb 10.4.26`.
I cannot connect to the database in any way; I can only view `error/mysql-error-running.log` which displays this:
```
[] Added new Mazter_info '' to hash table
[] /rdsdbbin/mysql/bin/mysqld: ready for connections.
Version: '10.4.25-MariaDB-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution
[] /rdsdbbin/mysql/bin/mysqld (initiated by: rdsadmin[rdsadmin] @ localhost []): Normal shutdown
[] Event Scheduler: Purging the queue. 8 events
[] InnoDB: FTS optimize thread exiting.
[] InnoDB: Buffer pool(s) load aborted due to user instigated abort at 221023 10:23:00
[] InnoDB: Dumping of buffer pool not started as load was incomplete
[] InnoDB: Starting shutdown...
[] InnoDB: Removed temporary tablespace data file: "ibtmp1"
[] InnoDB: Shutdown completed; log sequence number 14512830675889; transaction id 27562688049
[] /rdsdbbin/mysql/bin/mysqld: Shutdown complete
```
It appears the only option right now is to restore to the latest backup (the option to Reboot is unavailable), but I don't know if this will leave the database in an unstable/incomplete state.
Is there something else I could check or do? Should I just wait?
'**in_predicate_conversion_threshold**' does not appear to be available as an option in the MariaDB Parameter Groups
However, it's not listed as excluded in the 'MySQL parameters that aren't available'
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.MariaDB.Parameters.html
I can manually view/change its value, as follows:
* SELECT @@GLOBAL.in_predicate_conversion_threshold;
* SET in_predicate_conversion_threshold =0;
Is it possible to change the default '**in_predicate_conversion_threshold**' value via the AWS console or via a MariaDB Parameter Group?
Amazon RDS for MariaDB 10.3 will reach end of standard support on October 23, 2023. This follows MariaDB community's plan to deprecate MariaDB major version 10.3 on May 25, 2023 [1]. You will be able to run your Amazon RDS for MariaDB 10.3 databases between May 25, 2023 and October 23, 2023. However, these databases will not receive any security patches during this extended availability period. We strongly recommend you monitor the MariaDB community's security vulnerabilities page for documented CVE patches available in the latest versions [2].
We recommend that you proactively upgrade your databases to major version 10.6 before community deprecation of version 10.3 on May 25, 2023. Amazon RDS for MariaDB 10.6 introduced multiple features to enhance the performance, scalability, reliability and manageability of your workloads, including MyRocks storage engine, IAM integration, one-step multi-major upgrade, delayed replication, improved Oracle PL/SQL compatibility and Atomic DDL [3].
To learn more about upgrading MariaDB major versions in RDS, review the 'Major version upgrades for MariaDB' section in the Amazon RDS User Guide [4].
Starting August 23, 2023 12:01 UTC, you will not be able to create new RDS instances with MariaDB major version 10.3 from either the AWS Console or the CLI. We recommend you to upgrade your databases before October 23, 2023. RDS will upgrade your MariaDB 10.3 databases to MariaDB 10.6 during a scheduled maintenance window between October 23, 2023 12:01 UTC and January 23, 2024 12:01 UTC. On January 23, 2024 12:01 UTC, any MariaDB 10.3 databases that remain will be upgraded to version 10.6 regardless of instances' scheduled maintenance window.
To proactively plan for future Amazon RDS for MariaDB deprecation of major version 10.4 and above, you can refer to the release calendar in the Amazon RDS user guide [5].
If you have any questions or concerns, please reach out to AWS Support [6].
[1] https://mariadb.org/about/#maintenance-policy
[2] https://mariadb.com/kb/en/security/
[3] https://aws.amazon.com/about-aws/whats-new/2022/02/amazon-rds-mariadb-supports-mariadb-10-6/
[4] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.MariaDB.html
[5]https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MariaDB.Concepts.VersionMgmt.html#MariaDB.Concepts.VersionMgmt.ReleaseCalendar
[6] https://aws.amazon.com/support
asked 5 months ago