Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 Bug Report: migration fails with Allowed memory size exhausted php memory_limit hardcoded to 512 #5528

Closed
2 tasks done
bfritscher opened this issue May 13, 2023 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@bfritscher
Copy link

👟 Reproduction steps

Run a migration fails upgrading audit data, with out of memory

👍 Expected behavior

Expect the migration to work.
Or at least be able to specify a higher php memory_limit via environnment without the need to edit the app/init.php hardcoded value: ini_set('memory_limit', '512M');

👎 Actual Behavior

fails with php out of memory error

🎲 Appwrite version

Version 1.3.x

💻 Operating system

Linux

🧱 Your Environment

docker self hosted

👀 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?

@bfritscher bfritscher added the bug Something isn't working label May 13, 2023
@stnguyen90 stnguyen90 self-assigned this May 26, 2023
@stnguyen90
Copy link
Contributor

@bfritscher thanks for raising this issue! 🙏🏼 Interesting challenge... 🧐

For now, I would suggest either modifying this:

ini_set('memory_limit', '512M');

before running the migrate command.

@stnguyen90
Copy link
Contributor

@bfritscher, did the suggestion work for you?

@bfritscher
Copy link
Author

@stnguyen90 Thanks for following up. Yes, it is the workaround I described (and used) in my initial report, as well as the possible solution which would be to replace the hardcoded value with an environment variable. Another would be to identify which part of the migration process uses too much memory.

@bfritscher
Copy link
Author

Hi, @stnguyen90 the fix is only the workaround? Or do you plan to implement any of the above suggestions or any other fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants