Bug 1346288
Summary: | Server returning error 500 after large package upload | ||
---|---|---|---|
Product: | [Community] Copr | Reporter: | Helio Chissini de Castro <helio> |
Component: | frontend | Assignee: | clime |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | clime, fedora, msuchy |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-09-12 17:06:30 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Helio Chissini de Castro
2016-06-14 13:14:32 UTC
@clime you can test this on 0ad package http://koji.fedoraproject.org/koji/packageinfo?packageID=14762 It is probably biggest open source SRPM I ever seen - 1GB. But please test it on dev instance only, so it does not eat our storage on production too quickly. I tested it on the 0ad package and it went fine. The issue was caused by search index updates and this part is still a bit problematic cause the updates take ~1s (and even more) according to my tests so in rare cases the timeout 20s (current configured value) might not be enough. If that happens, we will probably opt to batch re-indexing a few times a day. The following commits were made to fix this issue: https://github.com/fedora-copr/flask-whooshee/commit/bef1253a https://github.com/fedora-copr/copr/commit/e26bb061 https://github.com/fedora-copr/copr/commit/c4654aad copr-frontend-1.97-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-2a2eeb10a9 copr-frontend-1.97-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-ec39f79e18 copr-frontend-1.97-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-2a2eeb10a9 copr-frontend-1.97-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-ec39f79e18 copr-frontend-1.97-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report. copr-frontend-1.99-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-c38bc25dbc copr-frontend-1.99-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-c38bc25dbc New Copr has been released. copr-frontend-1.101-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-5a3cdc5801 copr-frontend-1.101-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-5a3cdc5801 copr-frontend-1.101-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. |