This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| wiki:how_to_handle_a_bigger_and_bigger_oar_database [2016/06/29 14:09] – [Option 1: reset the database] neyron | wiki:how_to_handle_a_bigger_and_bigger_oar_database [2016/06/29 14:17] – [Option 1: reset the database] 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 18: | Line 18: | ||
| This solution is fairly easy, but with the drawback of breaking history (e.g. job dependency if any), and forcing to stop running jobs and emptying queues (i.e. breaking the continuity of service). | This solution is fairly easy, but with the drawback of breaking history (e.g. job dependency if any), and forcing to stop running jobs and emptying queues (i.e. breaking the continuity of service). | ||
| - | It involves to following | + | It involves to following |
| * initialize a new database using the oar-database tool | * initialize a new database using the oar-database tool | ||
| * typically with the same credentials as the former one | * typically with the same credentials as the former one | ||