#2292: Lock down resources on osgeo7
---------------------------+-------------------
Reporter: robe | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Keywords:
---------------------------+-------------------
Right now I haven't been putting any limits on cpu and memory that each
container is using so containers can freely use as much as they want.
Which is good and bad.
Good in that if resources aren't being used, we should make them
available. Bad becasue we could get a rogue container eating up resources
such as selfish process or some coin mining operation.
That said I'm going to start locking down resources especially on things
that really shouldn't be using that much in the way of resources.
So for example on secure -- it was a tiny container - only 20 GB in size.
There is no reason for that to grow much larger than that. (that's not
live yet though).
Right now our free mem on osgeo7 is reading
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2292>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.