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

Raise execution_time and memory_limit for Import Runs via Web UI #1954

Closed
Thomas-Gelf opened this issue Sep 23, 2019 · 1 comment
Closed
Assignees
Milestone

Comments

@Thomas-Gelf
Copy link
Contributor

When triggering Import Runs for large and/or slow Import Sources, this works fine on CLI and as a background job, but might fail when triggered from the Web Frontend when reaching configured PHP memory or execution time limits.

For v1.7.0 we'll just raise limits on demand accordingly (like we're already doing with sync and config deployments). With v1.8.0 this should be completely gone, as Import Runs will always be executed by the background daemon.

@Thomas-Gelf Thomas-Gelf added this to the 1.7.0 milestone Sep 23, 2019
@Thomas-Gelf Thomas-Gelf self-assigned this Sep 23, 2019
@Thomas-Gelf
Copy link
Contributor Author

With v1.8.0 this should be completely gone, as Import Runs will always be executed by the background daemon.

#1955 will address this part

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant