User story #14144
open
When pgsql is shutdown because partition is full, agent should also shutdown rudder web app
Added by François ARMAND over 5 years ago.
Updated over 3 years ago.
Category:
System integration
Description
To prevent grave data corruption on postgresql database, we have a policy on Rudder server that looks at partition size on DB and shutdown postgres if the partition is full.
The problem is that Rudder web app is still available, but seems broken / not up to date. We want to also shutdown jetty so that it is really apparent that something is not going as expected and that the user must take a look.
(not: this must be documented with a big warning to help people be aware that that behavior may happen).
We could/should also have a script that would clean database (purging indexes and recreating them concurrently), that would stop web interface, get current maintenace_mem ( select current_setting('maintenance_work_mem'); ), increase maintenance_work_mem (SET maintenance_work_mem TO '32 MB';), recreat indexes, restore old value of maintenance_work_mem, check free space, restart web interface
and we could either run it automatically when out of space (and not more often than once per X day), or strongly suggest to user to run it if rudder is stopped (change the loading page in case of malfunction?)
- Related to Bug #11739: When we have a /var full, Rudder LDAP or Postgres can be corrupted added
Shutdown doesn't work anymore in Rudder 5.0, as rudder is not a service anymore there, but rudder-server is
In 5.1 postgresql is not a dependency anymore of rudder, so shuting down rudder doesn't stop postgres anymore
Plus, we hsould definitively NOT stop postgresql automatically if rsyslog is in TCP, the risk is too high for the infrastructure
- Target version changed from 5.0.5 to 5.0.6
- Target version changed from 5.0.6 to 5.0.7
- Target version changed from 5.0.7 to 5.0.9
- Target version changed from 5.0.9 to 5.0.10
- Target version changed from 5.0.10 to 5.0.11
- Target version changed from 5.0.11 to 5.0.12
- Target version changed from 5.0.12 to 5.0.13
- Target version changed from 5.0.13 to 5.0.14
- Target version changed from 5.0.14 to 5.0.15
- Target version changed from 5.0.15 to 5.0.16
- Target version changed from 5.0.16 to 5.0.17
- Target version changed from 5.0.17 to 5.0.18
- Target version changed from 5.0.18 to 6.2.0~beta1
- Target version changed from 6.2.0~beta1 to 6.2.0~rc1
- Target version deleted (
6.2.0~rc1)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by