Set RLIMIT_AS for koji hub #6966

Closed
opened 2018-05-22 14:32:49 +00:00 by mikem · 6 comments
  • 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?

* 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?

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

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

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)
**Metadata Update from @kevin**: - Issue priority set to: Next Meeting (was: Waiting on Reporter)

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

🌆

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)
**Metadata Update from @kevin**: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Infrastructure/fedora-infrastructure#6966
No description provided.