Project

General

Profile

Actions

Bug #12670

closed

Memory problem

Added by Michele Artini over 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
_InfraScience Site Reliability Engineer (SRE)
Start date:
Oct 12, 2018
Due date:
% Done:

100%

Estimated time:

Description

Today I noticed that solr was died and I could not restart it.

Tommi has noticed that php-fpm was consuming a lot of memory, so we have increased the RAM to 10 GB.

Can you schedule a daily restart of php-fpm?


Add

Subtasks


Add

Related issues

Related to ISTI Open Access - Feature #11601: Migrate the OpenPortal services to production machinesClosed_InfraScience Site Reliability Engineer (SRE)Oct 12, 2018

Delete relationActions
Actions #1

Updated by Andrea Dell'Amico over 6 years ago

  • Assignee changed from Andrea Dell'Amico to _InfraScience Site Reliability Engineer (SRE)
Actions #2

Updated by Andrea Dell'Amico over 6 years ago

  • Related to Feature #11601: Migrate the OpenPortal services to production machines added

Updated by Andrea Dell'Amico over 6 years ago

It would be better to do the math for the maximum php memory consumption: there are limits to the max memory for each process and to the max number of processes, so the available RAM should be more that that total.
When we'll have a VM for each service this kind of measures will be easier, FYI.

Updated by Andrea Dell'Amico about 6 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Let's see what happens on the new service, where the PHP frontend runs into its own VM.

Actions

Also available in: Atom PDF