Set RLIMIT_AS for koji hub #6966
Labels
No labels
announcement
authentication
automate
aws
backlog
blocked
bodhi
ci
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Initiative Worthy
Closed As
Insufficient data
Closed As
Invalid
Closed As
Spam
Closed As
Upstream
Closed As
Will Not or Can Not fix
cloud
communishift
copr
database
deprecated
dev
discourse
dns
downloads
easyfix
epel
factory2
firmitas
gitlab
greenwave
hardware
help wanted
high-gain
high-trouble
iad2
koji
koschei
lists
low-gain
low-trouble
mbs
medium-gain
medium-trouble
mini-initiative
mirrorlists
monitoring
Needs investigation
notifier
odcs
OpenShift
ops
OSBS
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
rdu-cc
release-monitoring
releng
repoSpanner
request-for-resources
s390x
security
SMTP
src.fp.o
staging
taiga
unfreeze
waiverdb
websites-general
wiki
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Infrastructure/fedora-infrastructure#6966
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
set RLIMIT_AS in hub.conf for koji hub
There is no particular timeline
I recommend this setting be kept indefinitely
Without this setting, it is possible for some hub calls to consume arbitrary amounts of memory. This can lead to performance issues. It is better to set a reasonable RLIMIT_AS to limit how much memory an individual httpd process can use. Then, a overzealous query will get a memory error rather than having to be oom-killed.
I thought Fedora already had this setting in place at one point. Maybe it was lost when you guys moved to ansible?
Sure, we could do this, but will we hit problems with things like texlive's 2+GB src.rpm?
Is there a suggested value? Or some way to know what we are hitting now?
Metadata Update from @kevin:
I have noticed this ( https://pagure.io/koji/issue/941 ) which led to this issue being created.
Metadata Update from @kevin:
ok. I have set this now... please let us know if you see any problems with it.
🌆
Metadata Update from @kevin: