Getting Error: PDOException - MySQL server has gone away

It's why not >> 🤔 ? Is it or is it not? 😅

Sorry 😅😅 Why you think it's not sufficient?

Is that fixed your problem?

I just wanted to make sure that there is no other backup procedure for databases 😉 .

Ohh I got you So yes it's sufficient, I wrote you just to make sure you indeed backed up the database

ALTER TABLE _1_executions ENGINE=InnoDB;

it did work 🎉 Thank you sooo much! 🙏 <:appwriteheart2:1073243188954935387> But this shows, that there is somewhere a bug, isn't? Is it on the MariaDB side?

I'm not really sure The Search text index somehow get corrupted this is more for the AppWrite Team.

The problem is, that it really shutsdown the whole appwrite backend.

Yes indeed

it sounds like you're using the default mariadb container on the same server, right? how much memory does your server have?

It has 16GB RAM (dedicated Azure VM server). But the RAM is being used by a appwrite function, which uses a deep learning algorithm, which eats a lot of on usage RAM. So RAM shortage can't be ruled out.

hmmm ya that could be a problem. ideally, in a production system, you would separate mariadb into a dedicated server/cluster.

So the RAM shortage can lead to a not recoverable data corruption in the MariaDB?

Do I need to use some Kubernetes infrastructure to implement this?

No

AppWrite is ready for it out-of-the-box

What you need to do is to set your database in a separate server

Then update this values within the .env file

_APP_DB_HOST=mariadb
_APP_DB_PORT=3306
_APP_DB_SCHEMA=appwrite
_APP_DB_USER=user
_APP_DB_PASS=password
_APP_DB_ROOT_PASS=rootsecretpassword

And if you're using vpc you can enter the database local address

And also if you want to get into it AppWrite docker-compose file can be easily scalable using docker swarm (Although most of the scalability option would had to be done manually, but still)

So it's recommended to separate the database in production mode?

If you have a small to small-medium project then everything inside one docker-compose.yml should be just fine.

But if your application is about the grow, Then I think it is. When you're decentralizing your application parts you make it more sustainable and much more easy to maintain it in the long term.

Of course its good to remember to set a VPC between the databases and the actual Appwrite server.

And, BTW, In decentralizing I'm also referring to the two other databases include with Appwrite; Redis and InfluxDB.

Oh I see, hmm in a future if i go for appwrite cloud service do I need to do the same (I believe they will offer pretty good storage) !

If you use the cloud then you don't to worry about anything, Just your code and implementation, all the infrastructure is managed by Appwrite team

Uh-huh that's great, thanks 🙂