#6966 Set RLIMIT_AS for koji hub
Closed: Fixed 5 years ago Opened 5 years ago by mikem.

  • Describe what you need us to do:

set RLIMIT_AS in hub.conf for koji hub

  • When do you need this? (YYYY/MM/DD)

There is no particular timeline

  • When is this no longer needed or useful? (YYYY/MM/DD)

I recommend this setting be kept indefinitely

  • If we cannot complete your request, what is the impact?

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:
- Issue assigned to kevin
- Issue priority set to: Waiting on Reporter (was: Needs Review)

5 years ago

I have noticed this ( https://pagure.io/koji/issue/941 ) which led to this issue being created.

Metadata Update from @kevin:
- Issue priority set to: Next Meeting (was: Waiting on Reporter)

5 years ago

ok. I have set this now... please let us know if you see any problems with it.

:city_sunset:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata