matomo-org / matomo-org/plugin-Migration
Output error when server runs out of memory during migration
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 7
- Forks
- 11
- Avg merge
- 4h 17m
- Merged PRs (30d)
- 2
Description
As mentioned in #37 we had a customer who's migration kept failing at a certain point.
They then increased the available memory from 12gb to 24gb and the migration was able to finish.
During this process they said that there were no errors in the logs our output from the migration plugin that indicated what the error was, so they were forced to try different things until something worked (Such as increasing available memory)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the migration plugin's error and output handling, then determine how memory-related migration failures are reported; done means a failed migration produces a clear, actionable error in the migration output or logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100