This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| wiki:how_to_handle_a_bigger_and_bigger_oar_database [2016/06/29 14:08] – [Option 1: reset the database] neyron | wiki:how_to_handle_a_bigger_and_bigger_oar_database [2016/06/29 14:16] – neyron | ||
|---|---|---|---|
| Line 9: | Line 9: | ||
| However, some other installations (probably with a less powerful server) are known to have required some maintenance in order to keep OAR fully responsive. | However, some other installations (probably with a less powerful server) are known to have required some maintenance in order to keep OAR fully responsive. | ||
| - | Therefore, this page gathers some knowhow | + | Therefore, this page gathers some know-how |
| ====== Option 1: reset the database ====== | ====== Option 1: reset the database ====== | ||
| Line 27: | Line 27: | ||
| * admission rules: data (rows) of the admission_rules table | * admission rules: data (rows) of the admission_rules table | ||
| * make sure the cluster is empty of running jobs (you may use oarnodesetting --drain command) | * make sure the cluster is empty of running jobs (you may use oarnodesetting --drain command) | ||
| - | * empty the queues (waiting jobs): ask users to wait for the new database to be in service before submitting new jobs) | + | * empty the queues (waiting jobs): ask users to wait for the new database to be in service before submitting new jobs, an dedicated admission rule may help here) |
| * stop the oar-server | * stop the oar-server | ||
| * change the database in use, in oar.conf (server and frontend) | * change the database in use, in oar.conf (server and frontend) | ||