🐛 Bug Report: adding attribute in a large collection crashes

[AidenY69]

👟 Reproduction steps

Make a collection with over 40 million items, try adding a new attribute.

👍 Expected behavior

A new attribute should be added

👎 Actual Behavior

It crashes instead.

Is there a way to use command line to add a new attribute or some 'backdoor' method? Bash script to just run through every item in the database line by line?

🎲 Appwrite version

Version 1.3.x

💻 Operating system

Linux

🧱 Your Environment

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[joeyouss]

Hi @AidenY69
Answering your question - Yes it is possible but not recommended
Also, can you provide few details to me about whether you are using self hosted or cloud version, what is the error message?

[AidenY69]

Hi @AidenY69 Answering your question - Yes it is possible but not recommended Also, can you provide few details to me about whether you are using self hosted or cloud version, what is the error message?

1. we are using docker self-hosted version
2. error message from the appwrite worker-databases container is: "SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction"

[joeyouss]

hi @AidenY69 thank you for the update, I will be looking into it and get back to you : )

[fogelito]

Hey @AidenY69 , Can you show create the table structure, please? It is always better to add an attribute on such a big scale when you have minimum traffic. looks like you have exceeded the time for waiting for a lock which default is 50 sec.

[fogelito]

Is it possible to stop the writes for this collection, from somewhere in your code? or limit the traffic using this collection?
before adding the attribute?

[fogelito]

You can try setting innodb_lock_wait_timeout for more seconds like 120 seconds.

[AidenY69]

The website is actually complete shutdown (maiantence mode) when these operations occur, so 0 traffic. The lockout timeout was raised and still the same issue.

[fogelito]

What is the error you get in the appwrite-mariadb container?

[DH-555]

@AidenY69 Are you still experiencing this issue?

[github-actions]

This issue has been labeled as a 'question', indicating that it requires additional information from the requestor. It has been inactive for 7 days. If no further activity occurs, this issue will be closed in 14 days.

[github-actions]

This issue has been closed due to inactivity. If you still require assistance, please provide the requested information.