Questions tagged with MariaDB
Content language: English
Sort by most recent
I am trying to upgrade Maria DB version. (It's because aws has stopped supporting that version.)
The thing to worry about is that the DB endpoint and address such as ARN seem to have changed.
Does the version upgrade change values such as endpoints or ARNs?
Hi Everyone,
I have used RDS MariaDB with the option Autoscaling enable. I receive alarm feeble storage of more than 120GB. But actually, I did check size storage in Databases is 54GB with the command below:
```
SELECT table_schema "DB Name",
ROUND(SUM(data_length + index_length) / 1024 / 1024 / 1024, 1) "DB Size in GB"
FROM information_schema.tables
GROUP BY table_schema;
```
Please explain and help me resolve issues.
Best regard.
I wanted to connect to my database remotely and did some modifications to allow this. Followed the instructions in the [Connect To MariaDB From A Different Machine](https://docs.bitnami.com/virtual-machine/infrastructure/lamp/administration/connect-remotely-mariadb/) page. Hit a bump in the first step; the `ufw` command was not recognized. So I tried to find a way to install it and followed the instructions in the [-bash: ufw: command not found (ubuntu 18.04)](https://dev.to/delightfullynerdy/bash-ufw-command-not-found-ubuntu-18-04-1agh) page.
I did all that and now I can't connect to my instance. The site in the instance is inaccessible. Can't connect using SSH or FTP. Can't ping the IP.
Restarting the services and/or the instance did not work. If I click on the "Connect using SSH" button in the instance page (in the Lightsail console) and wait long enough, I get the following error:
> An error occurred and we were unable to connect or stay connected to your instance. If this instance has just started up, try again in a minute or two.
>
> UPSTREAM_NOT_FOUND [519]
How can I regain access to my instance back? If the instance is not salvagable, is there a way to, well, salvage the database (and maybe the project files)?
Hello,
I received an email from AWS saying I have an mandatory OS update for my RDS (MariaDB) in N.Virginia.
I have checked the Maintenance & backups section in the RDS console but found no OS update. There is only "Auto minor version upgrade".
I also have checked AWS Health Dashboard but found nothing on the "Open and recent issues", "Schedulled changes", "Other notification", and "Event log". They are all zero.
I also have checked the result of the command "aws rds describe-pending-maintenance-actions" and the result was:
{
"PendingMaintenenaceActions": []
}
I also have read the post ( https://repost.aws/questions/QUM7E7C5aaSsWZejFs2ev3zQ/rds-os-update-is-available-don-t-see-it-in-rds-dashboard ) but I'm still not sure what was going on.
Is the content of the email wrong or should I check it somewhere else?
What should I do?
hello.
Events related to OS upgrade have been confirmed as shown below.
> Health Events
> Here is a summary of the milestones related to the OS upgrade.
* You can now initiate OS upgrades at any time on Amazon RDS for affected MariaDB DB instances until August 31, 2022 at 9:01 AM KST.
* After August 31, 2022 at 9:01 AM KST, Amazon RDS will automatically upgrade the MariaDB DB instance's OS to the latest version within the maintenance window.
**RDS Settings**
- Engine Version: MariaDB 10.4.21
- Class: db.m5.xlarge
- Minor version auto-upgrade enabled.
There was maintenance work, so I applied it right away.
- Recommendation type applied: Enhanced monitoring off
Pending maintenance tasks are not checked in the RDS console.
How can I check if the upgrade is complete?
For RDS Mariadb, how do I check for recommendations?
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Maintenance.html#USER_UpgradeDBInstance.Maintenance.Multi-AZ
Thank you.
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?
What I'm doing is using AWS Lambda with Serverless-Express to host my Express API via AWS. I've done that for the most part, but my endpoints that attempt to query my MariaDB SkySQL database are not working, and from the CloudWatch logs it looks like the database connection is timing out.
I think the issue is that SkySQL isn't recognizing AWS Lambda as having proper permissions to access the database. In my SkySQL database I have to manually add IPv4 addresses that are allowed to query the database. **My question is, how do I get the IPv4 address(es), and/or is there a better way to do this?**
I've just tested RDS MariaDB snapshot export to S3. The snapshot is good, a test restore re-creates the database correctly. However, exporting that snapshot to S3 appears to succeed but no data is exported! The job summary and the metadata stored in the bucket both say the test DB was skipped, and the metadata claims the DB is empty (it isn't).
I'm working with a minimal test case and following the [AWS Console process as documented by AWS](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ExportSnapshot.html), including export all data (not a partial export). However, the resulting S3 export contains only the JSON meta-data files; no data appears in S3.
**Is this a known problem with RDS MariaDB service?**
export_tables_info_MyDbName-snapshot-test-2-after-stopping_from_1_to_1.json:
```
{
"perTableStatus": [
{
"warningMessage": {
"skippedDatabase": [
{
"reason": "DATABASE_IS_EMPTY"
}
]
},
"target": "MyDbName"
}
]
}
```
Amazon RDS is starting the end of life (EOL) process for MariaDB major engine version 10.2. We are doing this because the MariaDB community is planning to discontinue support for MariaDB 10.2 on May 23, 2022 \[1].
Amazon RDS for MariaDB 10.2 will reach end of life on October 15, 2022 00:00:01 AM UTC. While you will be able to run your Amazon RDS for MariaDB 10.2 databases between community MariaDB 10.2 EOL (May 23, 2022) and Amazon RDS for MariaDB 10.2 EOL (October 15, 2022), these databases will not receive any security patches during this extended availability period. We strongly recommend that you proactively upgrade your databases to major version 10.3 or greater before community EOL on May 23, 2022. MariaDB 10.3 offers improved Oracle compatibility, support for querying historical states of the database, features that increase flexibility for developers and DBAs, and improved manageability \[2]. Our most recent release, Amazon RDS for MariaDB 10.6, introduces multiple MariaDB 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]. If you choose to upgrade to MariaDB 10.6, you will be able to upgrade your MariaDB 10.2 instances seamlessly to Amazon RDS for MariaDB 10.6 in a single step, thus reducing downtime substantially. Both versions, MariaDB 10.3 and 10.6, contain numerous fixes to various software bugs in earlier versions of the database.
If you do not upgrade your databases before October 15, 2022, Amazon RDS will upgrade your MariaDB 10.2 databases to 10.3 during a scheduled maintenance window between October 15, 2022 00:00:01 UTC and November 15, 2022 00:00:01 UTC. On January 15, 2023 00:00:01 AM UTC, any Amazon RDS for MariaDB 10.2 databases that remain will be upgraded to version 10.3 regardless of whether the instances are in a maintenance window or not.
You can initiate an upgrade of your database instance to a newer major version of MariaDB — either immediately or during your next maintenance window — using the AWS Management Console or the AWS Command Line Interface (CLI). The upgrade process will shut down the database instance, perform the upgrade, and restart the database instance. The database instance may be restarted multiple times during the upgrade process. While major version upgrades typically complete within the standard maintenance window, the duration of the upgrade depends on the number of objects within the database. To avoid any unplanned unavailability outside your maintenance window, we recommend that you first take a snapshot of your database and test the upgrade to get an estimate of the upgrade duration. If you are operating an Amazon RDS for MariaDB 10.2 database on one of the retired instance types (t1, m1, m2), you will need to migrate to a newer instance type before upgrading the engine major version. To learn more about upgrading MariaDB major versions in Amazon RDS, review the Upgrading Database Versions page \[4].
We want to make you aware of the following additional milestones associated with upgrading databases that are reaching EOL.
**Now through October 15, 2022 00:00:01 AM UTC **- You can initiate upgrades of Amazon RDS for MariaDB 10.2 instances to MariaDB 10.3 or 10.6 at any time.
**July 15, 2022 00:00:01 AM UTC –** After this date and time, you cannot create new Amazon RDS instances with MariaDB 10.2 from either the AWS Console or the CLI. You can continue to restore your MariaDB 10.2 snapshots as well as create read replicas with version 10.2 until the October 15, 2022 end of support date.
**October 15, 2022 00:00:01 AM UTC -** Amazon RDS will automatically upgrade MariaDB 10.2 instances to version 10.3 within the earliest scheduled maintenance window that follows. After this date and time, any restoration of Amazon RDS for MariaDB 10.2 database snapshots will result in an automatic upgrade of the restored database to a still supported version at the time.
**January 15, 2023 00:00:01 AM UTC -** Amazon RDS will automatically upgrade any remaining MariaDB 10.2 instances to version 10.3 whether or not they are in a maintenance window.
If you have any questions or concerns, the AWS Support Team is available on AWS re:Post and via Premium Support \[5].
\[1] https://mariadb.org/about/#maintenance-policy
\[2] https://aws.amazon.com/about-aws/whats-new/2018/10/amazon-rds-now-supports-mariadb-10_3/
\[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.Upgrading.html
\[5] http://aws.amazon.com/support
asked a year ago
Hi Everyone,
Our application requires MariaDB 10.2 (or greater) or MySql 8 (or greater) for the use of recursive CTEs.
Is there any news on when this will be available to us via Aurora Serverless?
Thanks.
Hi, I've migrated a workload from mariadb on ec2 to rds and I'm facing a performance issue.
This job make massive update queries on some tables (69465).
Using mariadb service on Ec2 common instance (t3a.small) it takes **1m31,148s**
Using RDS (db.m6g.xlarge - storage io1 200GB ): **5m46,239s**
After many tries I realized that the only way to have the same performance on Ec2 and RDS is to disable "automated backups" on RDS
Can anybody help me to understand why? Backup is a requirement
[Latest RDS for MariaDB 10.6](https://aws.amazon.com/about-aws/whats-new/2022/02/amazon-rds-mariadb-supports-mariadb-10-6/) has support for storage engine MyRocks. What kind of workloads have you found that are best suited for it?
asked a year ago